Hi all.
It seems that we've reached at an agreement. We'll rename "full" scan.mode
to "latest-full" and "compacted" scan.mode to "compacted-full".
I've created a ticket about this [1] and will work on it soon.
[1] https://issues.apache.org/jira/browse/FLINK-30410
Shammon FY 于2022年12月12日周一 16:0
Hi jinsong, caizhi
Thank you for your reply.
I found that what really confused me was the starting position of the
streaming job to read data. As @caizhi mentioned in kafka, streaming jobs
only read incremental data and its definition is very clear. In the Table
Store, streaming jobs also have th
Thanks Shammon for bringing up the discussion.
My opinion is to combine everything into scan.mode so that we don't
have orthogonal options.
You first mention that there are two disadvantages for this solution.
*1. The behaviors of some StartupModes in Stream and Batch jobs are
inconsistent*
This
Thanks Shammon!
Your summary was very good and very detailed.
I thought about it again.
## Solution 1
Actually, according to what you said, there should be so many modes in theory.
- Runtime-mode: streaming or batch.
- Range: full or incremental.
- Position: Latest, timestamp, snapshot-id, compa
Hi devs:
I'm an engineer from ByteDance, and here I'd link to discuss "Scan mode in
Table Store for Flink Stream and Batch job".
Users can execute Flink Steam and Batch jobs on Table Store. In Table Store
0.2 there're two items which determine how the Stream and Batch jobs'
sources read data: Sta
