Retry fails if a non-ASCII string is used for the Kafka Record Key about decaton HOT 2 CLOSED

Hi, thanks for reporting the issue.

Yeah as you noticed, currently Decaton supports only String key for consumer records.
Though Decaton partially works somehow even with non-String keys to just processing tasks, there are several places that assuming keys are serialized with ascii-printable String.

Supporting only ascii-printable String was a design-decision that made in early days of Decaton that all tasks are assumed to be produced by DecatonClient.

However, now Decaton is kind of "general consumer framework" as it supports to consume messages in arbitrary-format, we think we should make Decaton to support also non-String keys.

FYI There is a in-progress effort to add non-String key support for Decaton (#61).

from decaton.

Thank you for your confirmation.

I have understood that there are early designs that support ASCII character keys.

By migrating the Kafka Topic key to an ASCII string, our problem has been resolved.
I think it would be very useful to support keys other than ASCII strings in the future, so I will watch #61.

from decaton.