/flink/blob/master/flink-connectors/flink-connector-files/src/main/java/org/apache/flink/connector/file/sink/FileSink.java
>
> Best,
> Guowei
>
>
> On Sun, Apr 24, 2022 at 11:39 AM Yi Tang wrote:
>
>>
>>
>> -- Forwarded message -
>> Fro
-- Forwarded message -
From: Yi Tang
Date: Sun, Apr 24, 2022 at 11:29 AM
Subject: Write to Aliyun OSS via FileSystem connector hang Job Master on
Finishing
To:
Hi team;
I'm trying to write to aliyun oss via FileSystem connector. The job master
always hangs on finishing.
Thanks Timo.
The whole idea is also based on the side output and output tag. Let me
explain it in detail:
1. Introduce a VirtualTableScan(or SideOutputTableScan), which can be
optimized as Physical RelNode. Then we can create a source catalog table
which will be converted to a VirtualTableScan, a
We can get a stream from a DataStream api by SideOutput. But it's hard to do
the same thing with Flink SQL.
I have an idea about how to get the late records while using Flink SQL.
Assuming we have a source table for the late records, then we can query late
records on it. Obviously, it's not a rea
operators or better
> optimization rules that create a smarter pipeline could change the
> entire topology with every major Flink version upgrade.
>
> Regards,
> Timo
>
> On 10.11.20 10:15, Yi Tang wrote:
> > Hi folks,
> >
> > A question about changing the top
Hi folks,
A question about changing the topology while upgrading a job submitted by
SQL.
Is it possible for now?
Looks like if we want to recover a job from a savepoint, it requires the
uid of the operator matches the corresponding one in the state. The
automatically generated uid depends largely
Hi Yun
Thanks for your quick reply.
To be clear, It's not essential to implement these features into the SQL
statement. And precisely because of the limitations of SQL, we want these
features happen.
1.
Yeah, I think the stream api also has not similar api. We want it because
sometimes we want to
Hi,
I'm looking for a way to handle potential errors in job submitted with SQL
API, but unfortunately nothing found.
Handle errors manually in SQL API is hard, I think. Is there a way to
handle all errors and send them to a SideOutput to avoid task failure.
Also one can put late records into a Sid
