What is your setting for schema.compatibility? I suspect the issue is
probably that it is defaulting to NONE which would cause the connector to
roll a new file when the schema changes (which will be frequent with data
that is interleaved with different schemas).
If you set it to BACKWARDS then the
Bumping this. Has anyone here observed this in their Kafka connect deployments?
Thanks,
Dave
On 5/26/17, 1:44 PM, "Dave Hamilton" wrote:
We are currently using the Kafka S3 connector to ship Avro data to S3. We
made a change to one of our Avro schemas and have noticed consumer throughput
Hi, does anyone have advice on how to deal with this issue? Is it possible that
changing a schema compatibility setting could correct it?
Thanks,
Dave
On 5/26/17, 1:44 PM, "Dave Hamilton" wrote:
We are currently using the Kafka S3 connector to ship Avro data to S3. We
made a change to on
