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 can inject a custom org.apache.kafka.clients.producer.Partitioner by implementing it and passing it through DecatonClientBuilder#producerConfig.
However, A decaton client wraps a task set by our application in DecatonTaskRequest.
So, to determine a partition based on a task in Partitioner, we should handle a DecatonTaskRequest (deserialize our defined task. after that proceed partition step) like the following.
The partition that is passed as the argument would be set to TaskMetadataProto and be used in an internal Partitioner that determines a partition base on it.
What do you think about this feature?
The text was updated successfully, but these errors were encountered:
We can inject a custom
org.apache.kafka.clients.producer.Partitioner
by implementing it and passing it throughDecatonClientBuilder#producerConfig
.However, A decaton client wraps a task set by our application in
DecatonTaskRequest
.So, to determine a partition based on a task in
Partitioner
, we should handle aDecatonTaskRequest
(deserialize our defined task. after that proceed partition step) like the following.The above seems redundant and Inefficient due to deserializing a serialized task.
Could we provide a way of specifying a partition in producing a task like the following API?
The partition that is passed as the argument would be set to
TaskMetadataProto
and be used in an internalPartitioner
that determines a partition base on it.What do you think about this feature?
The text was updated successfully, but these errors were encountered: