Jeremy Custenborder

@scheung38 Keys do not need to be unique. If you get two keys that are the same you will still get two records into Kafka. They will end up in...

I'm not sure on the KSQL part. I'd have to look into that. I think it doesn't support compound keys so you might need to use a single message transform...

Maybe. Given I don't fully understand this data I can't tell you for sure. You could also build a single message transform that concatenates a few fields. Think order-01:8:2020, etc....

Hey @bleporini Well timed PR! I was going to start some work on this very soon. I'm going to merge this into another branch and base my changes on it!...

@SledgeHammer01 I'll look into the metadata part. Have you tried using a unique file name? It could have something to do with how the connector handles restarts. Can you give...

Yea sorry about that. The 2.0 version has been in the works for quite a long time. I work for Confluent and Confluent will officially support it so we had...

Did you try this? sorry for the delay in responding. ```json { "name" : "org.apache.kafka.connect.data.Timestamp", "type" : "INT64", "version" : 1, "isOptional" : true } ```

Hi @mroiter-larus, Kafka Connect is a little weird. It has it's own type system that is independent to how the data is serialized. For example a Struct is basically a...

Off the top of my head I'm not sure. I don't know how much I would worry about it being schemaless or with schema. The converter could be Apache Kafka...

The schema generation feature can be a little difficult to use. In your case you really want the first file it processes to be have all of your columns. If...