You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/01/30 10:42:00 UTC
[jira] [Closed] (FLINK-10188) Solve nondeterministic functions
problem for retraction
[ https://issues.apache.org/jira/browse/FLINK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Young closed FLINK-10188.
------------------------------
Resolution: Unresolved
> 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
>
> Discussion on the [mailing list|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-does-flink-know-which-data-is-modified-in-dynamic-table-td22432.html].
> Currently, Retraction has not considered non-deterministic functions. For sql like:
> {code:java}
> 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)