[
https://issues.apache.org/jira/browse/FLINK-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22404:
-----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Document inconsistencies around +I and +U generation in retract streams
> -----------------------------------------------------------------------
>
> Key: FLINK-22404
> URL: https://issues.apache.org/jira/browse/FLINK-22404
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Table SQL / API
> Affects Versions: 1.12.2
> Reporter: Nico Kruber
> Priority: Major
> Labels: stale-major
>
> Filters can remove +I messages and let a new row start with +U; similarly,
> they can remove the +U after -U which should instead have been reported as
> -D. This makes the semantics described on
> [https://ci.apache.org/projects/flink/flink-docs-release-1.12/dev/table/streaming/dynamic_tables.html#table-to-stream-conversion]
> wrong which makes users believe they can rely on +U vs. +I and -U vs. -D.
> Either this needs to be fixed, or a disclaimer should be added to the
> respective paragraphs that +U/+I and -U/-D should be seem as the same.
>
> Example:
> {code:sql}
> CREATE TEMPORARY VIEW test_cardinality AS
> SELECT * FROM ( VALUES
> ('Alice', '[email protected]', ARRAY [ '[email protected]' ], 'Test Ltd'),
> ('Alice', '[email protected]', ARRAY [ '[email protected]' ], 'Test Ltd'),
> ('Alice', '[email protected]', ARRAY [ '[email protected]', '[email protected]' ],
> 'Test Ltd'))
> AS t ( name, email, aliases, company );
> {code}
> {code:sql}
> SELECT
> name,
> LEAD(CAST(company AS VARCHAR), 0) AS company
> FROM test_cardinality
> WHERE CARDINALITY(aliases) >= 2
> GROUP BY name;
> {code}
> vs.
> {code:sql}
> SELECT
> name,
> LEAD(CAST(company AS VARCHAR), 0) AS company
> FROM test_cardinality
> GROUP BY name
> HAVING COUNT(DISTINCT email) >= 2;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
