[
https://issues.apache.org/jira/browse/FLINK-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz closed FLINK-13168.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.10.0)
Implemented in:
master via: a1b1758a7beada90e408aa953a76637caef63a14
1.9 via: 8312dfa86d0b9670ec8b6caf0574cc0bc01c44e1
> clarify isBatch/isStreaming/isBounded flag in flink planner and blink planner
> -----------------------------------------------------------------------------
>
> Key: FLINK-13168
> URL: https://issues.apache.org/jira/browse/FLINK-13168
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Legacy Planner, Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> in blink planner & flink planner, there are many {{isBatch}} and
> {{isStreaming}} flags, they have different meaning in different place. which
> makes reader and coder crazy. especially in blink planner, Only
> {{StreamTableSource}} could be used for both batch and stream. is {{bounded
> StreamTableSource}} means batch, {{unbounded}} means stream ?
> we should make it clear:
> 1. {{isBatch}} in {{ConnectorCatalogTable}}, which tells if the
> tableSource/tableSink is {{BatchTableSource}}/{{BatchTableSink}}
> 2. {{isBatch}} in {{TableSourceQueryOperation}}, which tells if the
> tableSource is {{BatchTableSource}}
> 3. {{isStreaming}} in {{TableSourceTable}}, which tells if if the current
> table is on stream planner
> 4. {{bounded StreamTableSource}} could be used for both batch and stream,
> while {{unbounded StreamTableSource}} could only be used for stream.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
