JQ Zhu

Sorry for ambiguity, the message key type is kafka builtin long(not avro long), and the value type is avro.

Will do later, thanks

It seems that the kafka-long key is still parsed as avro-long type: 

Maybe the UI could let us select key/value type?

Long keys are consumed well by Conduktor: 

@tchiotludo FYI, here's our spring-boot kafka properties: ```yaml spring.kafka: properties: schema.registry.url: http://schema-registry.kafka specific.avro.reader: true consumer: keyDeserializer: org.apache.kafka.common.serialization.LongDeserializer valueDeserializer: io.confluent.kafka.serializers.KafkaAvroDeserializer producer: keySerializer: org.apache.kafka.common.serialization.LongSerializer valueSerializer: io.confluent.kafka.serializers.KafkaAvroSerializer ```

+1

From README: > In case your project contains a lot of files you might want to disable file monitoring via lsp-enable-file-watchers (you may use dir-locals). Is `dir-locals` for project root...

Tips about adding cloud_provider for private k8s posted here: https://github.com/hyperledger/bevel/issues/1001#issuecomment-1125908098

Any plan? I thought `decorator.datasource.datasource-proxy.count-query=true` would expose those metrics to actuator/prometheus.