[
https://issues.apache.org/jira/browse/FLINK-39259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais updated FLINK-39259:
--------------------------------------
Summary: Add TO_CHANGELOG built-in process table function (4.2.2.2 upsert
stream, flat mode) (was: Add TO_CHANGELOG built-in process table function
(4.2.2.2))
> Add TO_CHANGELOG built-in process table function (4.2.2.2 upsert stream, flat
> mode)
> -----------------------------------------------------------------------------------
>
> Key: FLINK-39259
> URL: https://issues.apache.org/jira/browse/FLINK-39259
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Gustavo de Morais
> Assignee: Gustavo de Morais
> Priority: Critical
> Fix For: 2.3.0
>
>
> This is the first implementation of TO_CHANGELOG. The idea is to implement
> the use cases one by one interactively. With this ticket we will write the
> first version which allows flat mapping of retract/upsert stream.
> Implement TO_CHANGELOG built-in PTF as specified in FLIP-564, section 4.2.2.2
> (retract/upsert stream to upsert stream, flat mode).
> TO_CHANGELOG converts a dynamic table (retract/upsert stream) into an
> append-only stream with an explicit operation code column. Each input row is
> emitted as an INSERT-only row with a string op column indicating the original
> RowKind. This is stateless - each event maps directly to one output record.
> SELECT * FROM TO_CHANGELOG(input => TABLE t PARTITION BY id)
> What's included:
> - Built-in function definition and type strategies
> - Runtime implementation
> - Table API interface
> - MAP literal support in OperatorBindingCallContext and
> CallBindingCallContext
> - Plan tests, semantic tests (SQL, Table API, convenience API)
> - Use-case test: LAG on upsert stream (previously impossible without
> TO_CHANGELOG, like other aggregation functions)
> - Documentation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
