[jira] [Updated] (FLINK-30294) Change table property key 'log.scan' to 'startup.mode' and add a default startup mode in Table Store

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

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

ASF GitHub Bot updated FLINK-30294:
-----------------------------------
    Labels: pull-request-available  (was: )

> Change table property key 'log.scan' to 'startup.mode' and add a default startup mode in Table Store
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30294
>                 URL: https://issues.apache.org/jira/browse/FLINK-30294
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table Store
>    Affects Versions: table-store-0.3.0
>            Reporter: Caizhi Weng
>            Assignee: Caizhi Weng
>            Priority: Major
>              Labels: pull-request-available
>
> We're introducing time-travel reading of Table Store for batch jobs. However this reading mode is quite similar to the "from-timestamp" startup mode for streaming jobs, just that "from-timestamp" streaming jobs only consume incremental data but not history data.
> We can support startup mode for both batch and streaming jobs. For batch jobs, "from-timestamp" startup mode will produce all records from the last snapshot before the specified timestamp. For streaming jobs the behavior doesn't change.
> Previously, in order to use "from-timestamp" startup mode, users will have to specify "log.scan" and also "log.scan.timestamp-millis", which is a little inconvenient. We can introduce a "default" startup mode and its behavior will base on the execution environment and other configurations. In this way, to use "from-timestamp" startup mode, it is enough for users to specify just "startup.timestamp-millis".



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