You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/01/18 15:21:00 UTC

[jira] [Closed] (FLINK-25693) User property 'auto.offset.reset' doesn't take precedence in case of scan.startup.mode= group-offsets

     [ https://issues.apache.org/jira/browse/FLINK-25693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Visser closed FLINK-25693.
----------------------------------
    Resolution: Duplicate

I'm suspecting that this is a duplicate of the linked issue

> User property 'auto.offset.reset' doesn't take precedence in case of scan.startup.mode= group-offsets
> -----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-25693
>                 URL: https://issues.apache.org/jira/browse/FLINK-25693
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.14.0, 1.13.3
>            Reporter: Gaurav Miglani
>            Priority: Major
>
> If we declare a  Kafka table with `scan.startup.mode`= group-offset along with Kafka auto.offset.reset policy, user property doesn't take precedence. I think there is an issue with the 2 files.
>  #  [KafkaDynamicSource.java|https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kafka/src/main/java/org/apache/flink/streaming/connectors/kafka/table/KafkaDynamicSource.java#L396] -> Line no. 396
>  # [OffsetsInitializer.java|https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/source/enumerator/initializer/OffsetsInitializer.java#L108]  -> Line No. 108
> I think in the case of group offset, we need to check if the user has configured auto.offset.reset parameter. If yes, we should set OffsetResetStrategy as per.
>  
> SO error:
> [https://stackoverflow.com/questions/70756264/flink-kafka-sql-set-auto-offset-reset]
>  
> Let me know if it is really an issue,  I will be happy to work on and fix this



--
This message was sent by Atlassian Jira
(v8.20.1#820001)