[
https://issues.apache.org/jira/browse/FLINK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587343#comment-16587343
]
Hequn Cheng commented on FLINK-10188:
-------------------------------------
Agree, we may have to sort through all the cases and then forbid directly or
add state to address the problem. The solution may also cover
[FLINK-9528|https://issues.apache.org/jira/browse/FLINK-9528].
> Solve nondeterministic functions problem for retraction
> -------------------------------------------------------
>
> Key: FLINK-10188
> URL: https://issues.apache.org/jira/browse/FLINK-10188
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Reporter: Hequn Cheng
> Priority: Major
>
> Currently, Retraction has not considered non-deterministic functions. For sql
> like:
> {code}
> source -> group by ->
> non-window join -> retract_sink
> source -> group by ->
> {code}
> The group by will send retract messages to join. However, if we add
> LOCALTIMESTAMP between group by and join, messages can not be retracted
> correctly in join, since join retract messages according to the whole row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
