[jira] [Updated] (FLINK-32732) auto offset reset should be exposed to user

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-32732:
-----------------------------------
    Labels: pull-request-available stale-major  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> auto offset reset should be exposed to user
> -------------------------------------------
>
>                 Key: FLINK-32732
>                 URL: https://issues.apache.org/jira/browse/FLINK-32732
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>    Affects Versions: 1.16.1
>            Reporter: xiaogang zhou
>            Priority: Major
>              Labels: pull-request-available, stale-major
>
> {code:java}
> // code placeholder
> maybeOverride(
>         ConsumerConfig.AUTO_OFFSET_RESET_CONFIG,
>         startingOffsetsInitializer.getAutoOffsetResetStrategy().name().toLowerCase(),
>         true); {code}
> now flink override the auto.offset.reset with the scan.startup.mode config, and user's explicit config does not take effect. I think maybe we should expose this to customer?
>  
> I think after consuming kafka records from earliest to latest, the scan.startup.mode should no longer influence the kafka scan behave. So I suggest change the override to false.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)