Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 Kafka Sink: Tombstone encoded partition doesn't support timebased partioning #732

Open
joaopmoniz opened this issue Mar 14, 2024 · 0 comments

Comments

@joaopmoniz
Copy link

Hi there,

We are consuming the tombstones following the documentation, and the messages are stored in the path defined at tombstone.encoded.partition. We would like to also have the tombstone messages would be partitioned by a time based partition, which is the same we are using for regular messages, but this doesn't seem to be supported.
I would like to confirm if it's not supported, and ask for adding this as a feature if it's the case.

A simple S3 sink config to show this pattern would be the following:

  ...
  s3.bucket.name: "bucket"
  topics.dir: "kafka"
  partitioner.class: "io.confluent.connect.storage.partitioner.TimeBasedPartitioner"
  path.format: "YYYY/MM/dd/HH/"
  time.interval: "HOURLY"
  partition.duration.ms: "3600000"
  locale: "en-US"
  timezone: "UTC"
  store.kafka.keys: "true"
  behavior.on.null.values: "write"
  tombstone.encoded.partition: "tombstones"

What we would expect:

Regular messages:
s3://bucket/kafka/topic_name/YYYY/MM/DD/HH/message.format
s3://bucket/kafka/topic_name/YYYY/MM/DD/HH/message.keys.format

Tombstones:
s3://bucket/kafka/topic_name/tombstones/YYYY/MM/DD/HH/message.keys.format

What we have:

Regular messages:
s3://bucket/kafka/topic_name/YYYY/MM/DD/HH/message.format
s3://bucket/kafka/topic_name/YYYY/MM/DD/HH/message.keys.format

Tombstones:
s3://bucket/kafka/topic_name/tombstones/message.keys.format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant