THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
DefaultPartitioner
andUniformStickyPartitioner
will be deprecated, they'll behave the same way as they are today.- Users that don't specify a custom partitioner would get the new behavior automatically.
- Users that explicitly specify
DefaultPartitioner
orUniformStickyPartitioner
would get a deprecation warning, but see no change of behavior. They would need to update the configuration correspondingly to get the updated behavior (remove partitioner.class setting and optionally set partitioner.ignore.keys to 'true' if replacingUniformStickyPartitioner
).Users can continue to use their own partitioners -- if they want to implement a partitioner that switches partitions based on batch creations, they can use the onNewBatch(String topic, Cluster cluster) method to implement the feature Partitioner.onNewBatch
will be deprecated.
Rejected Alternatives
KafkaProducer to Explicitly Check for DefaultPartitioner
...