Could not reset offsets to earliest to get the stream from beginning for KTable

Hey,

I am using spring cloud kafka binder to read the data to KStream. While reading the data from one of the topic, i need to read from beginning.

I have tried to set kafka offset reset and start offset properties. But, could not find any references.

Could you please help me providing any sample application.yaml to reset the offset, so that i can consume messages from topic from the beginning

Adding application.yaml that i have used:

spring.cloud.stream.bindings.input:
  destination: input-topic1
  consumer:
    useNativeDecoding: true
    headerMode: raw
spring.cloud.stream.bindings.output:
  destination: output-topic
  producer:
    useNativeDecoding: true
    headerMode: raw
spring.cloud.stream.bindings.beginningInput:
  destination: beginning-topic
  consumer:
    useNativeDecoding: true
    headerMode: raw
spring.cloud.stream.kafka.streams.bindings.input:
  consumer:
    keySerde: org.apache.kafka.common.serialization.Serdes$StringSerde
    valueSerde: org.apache.kafka.common.serialization.Serdes$StringSerde
spring.cloud.stream.kafka.streams.bindings.output:
  producer:
    keySerde: org.apache.kafka.common.serialization.Serdes$StringSerde
    valueSerde: org.apache.kafka.common.serialization.Serdes$StringSerde
spring.cloud.stream.kafka.streams.bindings.beginningInput:
  consumer:
    keySerde: org.apache.kafka.common.serialization.Serdes$StringSerde
    valueSerde: org.apache.kafka.common.serialization.Serdes$StringSerde
    resetOffsets: true
    startOffset: earliest
spring.cloud.stream.kafka.streams.binder:
  brokers: 127.0.0.1
  zkNodes: 127.0.0.1
  configuration:
    default.key.serde: org.apache.kafka.common.serialization.Serdes$StringSerde
    default.value.serde: org.apache.kafka.common.serialization.Serdes$StringSerde
    commit.interval.ms: 1000

I would like to know if there is any error in the configuration i have used

[garyrussell]

@forgetaboutme As stated several times above; that property has no meaning (it is ignored by the kafka client) when there is already a committed offset for the consumer group; it only applies the first time a consumer consumes from a partition, or if it never commits an offset, or if the offsets have expired (by default, 7 days after the last consumer left the group with Brokers 2.1 and above).

[sobychacko]

@forgetaboutme This issue is very old and closed. Could you please start a new GH issue with the same details above? By “suggestions”, I meant the ones from @orchesio on May/2018 above, but happy to look into it further, if you can create a new issue with some context around it.