[
https://issues.apache.org/jira/browse/FLINK-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100373#comment-17100373
]
Kurt Young commented on FLINK-16998:
------------------------------------
Keep internal row's header makes sense, especially when we want to use a single
row to represent an update message which essentially consists of two messages:
update_before and update_after. I would imagine that will be printed as:
+U(-UB(a, 2), +UA(a, 3))
> Add a changeflag to Row type
> ----------------------------
>
> Key: FLINK-16998
> URL: https://issues.apache.org/jira/browse/FLINK-16998
> Project: Flink
> Issue Type: Sub-task
> Components: API / Core
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
>
> In Blink planner, the change flag of records travelling through the pipeline
> are part of the record itself but not part of the logical schema. This
> simplifies the architecture and API in many cases.
> Which is why we aim adopt the same mechanism for
> {{org.apache.flink.types.Row}}.
> Take {{tableEnv.toRetractStream()}} as an example that returns either Scala
> or Java {{Tuple2<Boolean, Row>}}. For FLIP-95 we need to support more update
> kinds than just a binary boolean.
> This means:
> - Add a changeflag {{RowKind}} to to {{Row}}
> - Update the {{Row.toString()}} method
> - Update serializers in backwards compatible way
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
