You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per Avro specification 1.11.0, logical-types Timestamp (millisecond precision) should be supported. Until kafka-rest version 6.2.14 it's working fine. I found that starting v7, this is broken.
How to reproduce
To demonstrate the issue, use the AVRO schema below:
{
"type": "record",
"name": "Key",
"namespace": "com.example",
"doc": "Avro schema for Kafka Key",
"fields": [
{
"name": "firstName",
"type": "string",
"doc": "First name of the user"
},
{
"name": "lastName",
"type": "string",
"doc": "last name of the user"
},
{
"name": "timestamp",
"type": {
"type": "long",
"logicalType": "timestamp-millis"
},
"doc": "Timestamp in number of milliseconds from the unix epoch"
}
]
}
I think setting 'avro.use.logical.type.converters=true' for the AvroSerializer somewhere might fix it but I'm not sure how to set it as an environment variable so it's taken into account...
I think setting 'avro.use.logical.type.converters=true' for the AvroSerializer somewhere might fix it but I'm not sure how to set it as an environment variable so it's taken into account...
I think we can't set 'avro.use.logical.type.converters=true' without this: 176d4b5
But it's only coming in v7.7...
I'm encountering what I believe to be the same issue when trying to serialise UUIDs.
However, it looks to me as if older versions of kafka-rest are compatible with newer versions of the other tools from the confluent-stack. So pinning kafka-rest to an older version and upgrading the rest of the stack appears to work, at least for my use cases.
Background
As per Avro specification 1.11.0, logical-types Timestamp (millisecond precision) should be supported. Until kafka-rest version 6.2.14 it's working fine. I found that starting v7, this is broken.
How to reproduce
To demonstrate the issue, use the AVRO schema below:
Sample Request:
Error:
The text was updated successfully, but these errors were encountered: