[
https://issues.apache.org/jira/browse/FLINK-17128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082998#comment-17082998
]
Jingsong Lee commented on FLINK-17128:
--------------------------------------
Hi [~twalthr], yes, this is just a temporary solution for old table connector
factory. "The difference between batch and streaming is very clear" is just for
old connector factory.
For long-term planning, we have discussed offline, our goal is to unify batch
and streaming, but there are two sets of operators for batch and streaming.
Batch operator is for optimizing performance in special scenarios.
So how to choose which set of operators:
# A operator can know its input boundedness, actually, this is from
Source.getBoundedness.
# A operator can know the emit strategy, like emit end of input, emit per
record, and etc...
Batch is just a special scene optimization of stream. So only "input bounded" +
"emit end of input" can use batch operators.
We can pass the "input boundedness" and "emit strategy" information to sink,
what do you think?
CC: [~jark] [~ykt836]
> Add isBounded to TableSinkFactory#Context
> -----------------------------------------
>
> Key: FLINK-17128
> URL: https://issues.apache.org/jira/browse/FLINK-17128
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Affects Versions: 1.11.0
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For current table environment, the difference between batch and streaming is
> very clear.
> We can use this bool to distinguish batch and streaming.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
