You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
What we would expect:
What we have:
The text was updated successfully, but these errors were encountered: