[
https://issues.apache.org/jira/browse/FLINK-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327844#comment-17327844
]
Flink Jira Bot commented on FLINK-17550:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> set a retract switch
> --------------------
>
> Key: FLINK-17550
> URL: https://issues.apache.org/jira/browse/FLINK-17550
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Cheng Shi
> Priority: Major
> Labels: stale-major
>
> During the execution of flink, especially the sql API, many operations in
> DataStream are not available. In many cases, we don't care about the DELETE
> record when retracting. Is it possible to set a switch so that the DELETE
> record when retracting is not processed? In other words, the downstream only
> receives a value after UPDATE, and does not need to receive the value before
> UPDATE. In some programming modes, processing DELETE records actually makes
> the logic more complicated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
