Ilya Kuramshin

Hello @christoph110, This behaviour is actually expected. Current json rendering policy is following json encoding spec for avro (https://avro.apache.org/docs/1.11.1/specification/_print/#json-encoding). Reason why this is required is that for some types like...

Hello @nitin1677, thank you for issues. Currently timestamp/offsets seeks are broken in our master branch. Can you please try using image with "latest" tag?

should be fixed after https://github.com/provectus/kafka-ui/issues/2624 is done

relates to ISSUE: https://github.com/provectus/kafka-ui/issues/1356

@Haarolean I suggest to add this to next release worklog, since this already affected some users in a bad way

Hello @SergKam , can you pls attach full log for latest exception?

> > Hello @SergKam , can you pls attach full log for latest exception? > > @iliax No, sorry. It was just an experiment, we decided not to use AWS...

error occurs when converting recursive avro schema to json schema (stackoverflow in AvroJsonSchemaConverter) example failing schema ``` { "type": "record", "name": "Anything", "namespace": "io.confluent.connect.avro", "fields": [ { "name": "somekey", "type":...

Hello @ekeric13 Thank you for the ticket. Behaviour you provided is expected, since offset/timestamp selection doesnt provided sorting. It only provides the way to seek to specific position where we...

NOTE currently timestamp/offset seek functionality broken in master branch. should be fixed after https://github.com/provectus/kafka-ui/issues/2624