-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[FLINK-39538][table] Support upsert output mode for FROM_CHANGELOG #28164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
20f0da0
091ac6c
41ce0e3
3ea26f3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -226,6 +226,18 @@ public interface PartitionedTable { | |||||
| * <p>For row semantics (each row processed independently), use {@link Table#fromChangelog} on | ||||||
| * the unpartitioned table. | ||||||
| * | ||||||
| * <p>Output changelog mode: | ||||||
| * | ||||||
| * <ul> | ||||||
| * <li><b>Retract</b> (default): the active {@code op_mapping} includes {@code UPDATE_BEFORE} | ||||||
| * or no updates at all. The output possibly emits {@code INSERT}, {@code UPDATE_BEFORE}, | ||||||
| * {@code UPDATE_AFTER}, and {@code DELETE}. | ||||||
| * <li><b>Upsert</b>: the {@code op_mapping} maps {@code UPDATE_AFTER} without {@code | ||||||
| * UPDATE_BEFORE}. The output emits {@code INSERT}, {@code UPDATE_AFTER}, and full {@code | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. removed
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmmm, it wasn't :D. I see "full" |
||||||
| * DELETE}, keyed on the partition columns. An upsert mapping without {@code PARTITION BY} | ||||||
| * is rejected at validation time, since upsert mode requires a key. | ||||||
| * </ul> | ||||||
| * | ||||||
| * <p>Examples: | ||||||
| * | ||||||
| * <pre>{@code | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The note is a bit repetitive, we already stated that it's an upsert table and we have explicit above that the partition by is required