If there is a "’Sink: Unnamed" operator using pure SQL, I think we should
improve this to give a meaningful operator name.
On Tue, 4 Aug 2020 at 21:39, godfrey he wrote:
> I think we assign a meaningful name to sink Transformation
> like other Transformations in StreamExecLegacySink/BatchExecLe
I think we assign a meaningful name to sink Transformation
like other Transformations in StreamExecLegacySink/BatchExecLegacySink.
Paul Lam 于2020年8月4日周二 下午5:25写道：
> Hi Jingsong,
>
> Thanks for your input. Now I understand the design.
>
> I think in my case the StreamingFileCommitter is not chai
Hi Jingsong,
Thanks for your input. Now I understand the design.
I think in my case the StreamingFileCommitter is not chained because its
upstream operator is not parallelism 1.
BTW, it’d be better if it has a more meaningful operator name.
Best,
Paul Lam
> 2020年8月4日 17:11，Jingsong Li 写道：
>
Hi Paul,
It is a meaningless sink.
This is because for the sake of flexibility, the `StreamingFileCommitter`
is implemented as a `StreamOperator` rather than a `SinkFunction`.
But `StreamTableSink` requires a `SinkFunction`, so we give a meaningless
`DiscardingSink` to it. And this sink should b
Hi,
I noticed that a simple SQL like 'insert into hive_parquet_table select … from
some_kafka_table' will generates an additional operator called ’Sink: Unnamed’
with parallelism 1. I wonder if it’s by design? And what’s the functionality of
this operator?
Thanks in advance!
Env:
- Flink 1.
