Re: Table API function and expression vs SQL

[ravi_suryavanshi.yahoo.com via user]

 Hi,we have decided to use the Table API using Flink SQL syntax (NOT JAVA). Can 
SQL syntax be changed in the higher version?as per the doc "SQL support is 
based on Apache Calcite which implements the SQL standard."
Thanks & Regards,RaviOn Saturday, 25 March, 2023 at 06:21:49 pm IST, Mate 
Czagany  wrote:  
 
 Hi,
Please also keep in mind that restoring existing Table API jobs from savepoints 
when upgrading to a newer minor version of Flink, e.g. 1.16 -> 1.17 is not 
supported as the topology might change between these versions due to optimizer 
changes.
See here for more information: 
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/concepts/overview/#stateful-upgrades-and-evolution
Regards,Mate

Hang Ruan  ezt írta (időpont: 2023. márc. 25., Szo, 
13:38):

Hi, 
I think the SQL job is better. Flink SQL jobs can be easily shared with others 
for debugging. And it is more suitable for flow batch integration.For a small 
part of jobs which can not be expressed through SQL, we will choose a job by 
DataStream API.
Best,Hang
ravi_suryavanshi.yahoo.com via user  于2023年3月24日周五 
17:25写道：

Hello Team,Need your advice on which method is recommended considering don't 
want to change my query code when the Flink is updated/upgraded to the higher 
version.
Here I am seeking advice for writing the SQL using java code(Table API  
function and Expression) or using pure SQL.
I am assuming that SQL will not have any impact if upgraded to the higher 
version.
Thanks and Regards,Ravi

  

Re: Task Failure Strategy for Adaptive Scheduler

[Weihua Hu]

Hi,

AFAIK, the reactive mode always restarts the whole pipeline now.

Best,
Weihua


On Tue, Apr 11, 2023 at 8:38 AM Talat Uyarer via user 
wrote:

> Hi All,
>
> We use Flink 1.13 with reactive mode for our streaming jobs. When we have
> an issue/exception on our pipeline. Flink rescheduled all tasks. Is there
> any way to reschedule only task that had exceptions ?
>
> Thanks
>

Re: 退订

[Weihua Hu]

退订请发送任意邮件到 user-unsubscr...@flink.apache.org，可以参考[1]

[1]
https://flink.apache.org/community.html#how-to-subscribe-to-a-mailing-list

Best,
Weihua


On Mon, Apr 10, 2023 at 9:04 AM 柒朵 <1303809...@qq.com> wrote:

> 退订
>

Task Failure Strategy for Adaptive Scheduler

[Talat Uyarer via user]

Hi All,

We use Flink 1.13 with reactive mode for our streaming jobs. When we have
an issue/exception on our pipeline. Flink rescheduled all tasks. Is there
any way to reschedule only task that had exceptions ?

Thanks

Re: emitValueWithRetract issue

[Adam Augusta]

Many thanks for the sanity check, Feng.

It’s a shame this well-documented feature was silently removed. emitValue()
creates an unreasonable amount of unnecessary and disruptive chatter on the
changelog stream, as evidenced by putting a print table after the
flatAggregate. Lots of -D/+I RowData pairs with identical fields.

Is there any clean way to set up a stateful group aggregation in the 1.18
Table API that doesn’t misbehave in this fashion?

On Mon, Apr 10, 2023 at 11:43 AM Feng Jin  wrote:

> hi Adam
>
> I have checked the code and indeed this feature is not available in the
> latest version of Flink code.
>
> This feature was originally implemented in the old planner:
> 
> https://github.com/apache/flink/pull/8550/files
>
> However, this logic was not implemented in the new planner , the Blink
> planner.
>
> With the removal of the old planner in version 1.14
> https://github.com/apache/flink/pull/16080 , this code was also removed.
>
>
>
> Best
>
> Feng
>
> On Sat, Apr 8, 2023 at 4:17 AM Adam Augusta  wrote:
>
>> The TableAggregateFunction javadocs indicate that either "emitValue" or
>> "emitUpdateWithRetract" is required.
>>
>> But if I implement my TableAggregateFunction with
>> "emitUpdateWithRetract", I get a validation error. If I implement both
>> methods it works, but emitUpdateWithRetract is not used.
>>
>> Peering into the Flink source code, I see that
>> ImperativeAggCodeGen validates the presence of emitValue, but is agnostic
>> to emitUpdateWithRetract.
>> More curiously, Flink's source code doesn't have a single test with a
>> TableAggregateFunction that uses emitUpdateWithRetract.
>>
>> Is this a ghost feature?
>>
>> Thanks,
>> Adam
>>
>

Re: emitValueWithRetract issue

[Feng Jin]

hi Adam

I have checked the code and indeed this feature is not available in the
latest version of Flink code.

This feature was originally implemented in the old planner:

https://github.com/apache/flink/pull/8550/files

However, this logic was not implemented in the new planner , the Blink
planner.

With the removal of the old planner in version 1.14
https://github.com/apache/flink/pull/16080 , this code was also removed.



Best

Feng

On Sat, Apr 8, 2023 at 4:17 AM Adam Augusta  wrote:

> The TableAggregateFunction javadocs indicate that either "emitValue" or
> "emitUpdateWithRetract" is required.
>
> But if I implement my TableAggregateFunction with "emitUpdateWithRetract",
> I get a validation error. If I implement both methods it works, but
> emitUpdateWithRetract is not used.
>
> Peering into the Flink source code, I see that
> ImperativeAggCodeGen validates the presence of emitValue, but is agnostic
> to emitUpdateWithRetract.
> More curiously, Flink's source code doesn't have a single test with a
> TableAggregateFunction that uses emitUpdateWithRetract.
>
> Is this a ghost feature?
>
> Thanks,
> Adam
>