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
It is pass the same partitions map for doInitialSeeks and onPartitionsAssigned
Likely that using new TopicPartitionOffset("foo", 0, System.currentTimeMillis(), SeekPosition.TIMESTAMP) (for END) new TopicPartitionOffset("foo", 0, 0, SeekPosition.TIMESTAMP) (for BEGINNING)
could workaround.
The text was updated successfully, but these errors were encountered:
Resolvesspring-projects#2178
The wrong collection was used as the source for the `assignments` map,
`SeekPosition.BEGINNING` and `.END` entries are removed; use the
`definedPartitions` field instead.
**cherry-pick to 2.8.x, 2.7.x**
Resolves#2178
The wrong collection was used as the source for the `assignments` map,
`SeekPosition.BEGINNING` and `.END` entries are removed; use the
`definedPartitions` field instead.
**cherry-pick to 2.8.x, 2.7.x**
Resolves#2178
The wrong collection was used as the source for the `assignments` map,
`SeekPosition.BEGINNING` and `.END` entries are removed; use the
`definedPartitions` field instead.
**cherry-pick to 2.8.x, 2.7.x**
Resolves#2178
The wrong collection was used as the source for the `assignments` map,
`SeekPosition.BEGINNING` and `.END` entries are removed; use the
`definedPartitions` field instead.
**cherry-pick to 2.8.x, 2.7.x**
# Conflicts:
# spring-kafka/src/main/java/org/springframework/kafka/listener/KafkaMessageListenerContainer.java
In what version(s) of Spring for Apache Kafka are you seeing this issue?
2.8.2
Describe the bug
When using a custom ContainerFactory that create
ContainerProperties(TopicPartitionOffset)
with
SeekPosition.END
ConsumerSeekAware.onPartitionsAssigned
will receive an empty map.To Reproduce
A custom ContainerFactory that does not use consumer group
Expected behavior
onPartitionsAssigned()
should receive assignments thateither
** Study **
I've inspected code in https://github.com/spring-projects/spring-kafka/blob/2.8.x/spring-kafka/src/main/java/org/springframework/kafka/listener/KafkaMessageListenerContainer.java#L2933
.
It is pass the same
partitions
map fordoInitialSeeks
andonPartitionsAssigned
Likely that using
new TopicPartitionOffset("foo", 0, System.currentTimeMillis(), SeekPosition.TIMESTAMP)
(for END)new TopicPartitionOffset("foo", 0, 0, SeekPosition.TIMESTAMP)
(for BEGINNING)could workaround.
The text was updated successfully, but these errors were encountered: