Hi, Timo.
Thank you for this great work! When I previously introduced the session window
TVF, I was contemplating
how to enable users to define a PTF in SQL. I'm glad to see this work being
discussed and that it has
improved the integration with the DataStream API.
After reading the entire
LvYanquan created FLINK-36648:
-
Summary: bump flink version to 2.0-preview1 for Kafka connector
Key: FLINK-36648
URL: https://issues.apache.org/jira/browse/FLINK-36648
Project: Flink
Issue Type:
Wenkai Qi created FLINK-36647:
-
Summary: Support TimestampDiff function in cdc pipeline transform
Key: FLINK-36647
URL: https://issues.apache.org/jira/browse/FLINK-36647
Project: Flink
Issue Type
Hi Tom,
Thanks for volunteering here
I would suggest rewriting in a similar way as it was done for 1.20.
We could rewrite Calcite dependency like it is done with others (for
instance Janino)
about Calcite
As you mentioned there are multiple JIRA issues for Calcite upgrade
somewhere in the past t
Rob Young created FLINK-36646:
-
Summary: Support Java 17+ job images more conveniently in the
operator
Key: FLINK-36646
URL: https://issues.apache.org/jira/browse/FLINK-36646
Project: Flink
Issu
Sai Sharath Dandi created FLINK-36645:
-
Summary: Gracefully handle null execution plan from autoscaler
Key: FLINK-36645
URL: https://issues.apache.org/jira/browse/FLINK-36645
Project: Flink
Thomas Cooper created FLINK-36643:
-
Summary: Upgrade aws-java-sdk-core to 1.12.773+ to fix
vulnerability
Key: FLINK-36643
URL: https://issues.apache.org/jira/browse/FLINK-36643
Project: Flink
Dawid Wysakowicz created FLINK-36644:
Summary: TIMESTAMPDIFF can not be string serialized
Key: FLINK-36644
URL: https://issues.apache.org/jira/browse/FLINK-36644
Project: Flink
Issue Type
Fabian Hueske created FLINK-36642:
-
Summary: Table API expressions with several built-in functions are
not correctly serialized to SQL
Key: FLINK-36642
URL: https://issues.apache.org/jira/browse/FLINK-36642
Hey Folks,
I am new to Flink development and wanted to get my hands dirty by fixing some
CVEs.
## Flink Table
I[raised
this](https://apache-flink.slack.com/archives/C03GV7L3G2C/p1729865902686739)
previouslyon the #dev slack channel. Currently the flink-table-runtime is using
a version (2.7.0
Hi everyone,
thanks for all the feedback I received so far. I had very healthy
discussions with various people both online and offline at Current and
Flink Forward Berlin. The general user responses were also very
positive. The FLIP should be ready to start a VOTE thread.
This is the last ca
+1 for the release and release manager candidate
Best,
Leonard
> 2024年10月31日 下午8:04，Yanquan Lv 写道：
>
> +1 for the release HBase connector 4.0 with 1.18 and 1.19 support.
>
>> 2024年10月29日 00:03，Ferenc Csaky 写道：
>>
>> Hi,
>>
>> Based on this discussion I would like to suggest to move on with
LvYanquan created FLINK-36641:
-
Summary: Support and Release Connectors for Flink 1.20
Key: FLINK-36641
URL: https://issues.apache.org/jira/browse/FLINK-36641
Project: Flink
Issue Type: Improveme
Matyas Orhidi created FLINK-36640:
-
Summary: Provide an easy way to reset autoscaling
Key: FLINK-36640
URL: https://issues.apache.org/jira/browse/FLINK-36640
Project: Flink
Issue Type: Improv
Dawid Wysakowicz created FLINK-36639:
Summary: Use table aliases in Table API asSerializableString
Key: FLINK-36639
URL: https://issues.apache.org/jira/browse/FLINK-36639
Project: Flink
I
Weijie Guo created FLINK-36638:
--
Summary: Remove legacy bounded blocking shuffle
Key: FLINK-36638
URL: https://issues.apache.org/jira/browse/FLINK-36638
Project: Flink
Issue Type: Bug
+1 for the release HBase connector 4.0 with 1.18 and 1.19 support.
> 2024年10月29日 00:03，Ferenc Csaky 写道：
>
> Hi,
>
> Based on this discussion I would like to suggest to move on with
> the originally planned release with the HBase connector 4.0, that
> will support 1.18, and 1.19.
>
> I voluntee
Elphas Toringepi created FLINK-36637:
Summary: Fix ListShards for Kinesis streams with large number of
shards
Key: FLINK-36637
URL: https://issues.apache.org/jira/browse/FLINK-36637
Project: Flink
Hi, Shengkai.
Thanks for driving this great work. LGTM overall, I just have one question.
IIUC, application mode supports to run multi-execute in a single `main`
function[1]. Does that means
we will support multi DMLs, multi DQLs, mixed DMLs & DQLs in one sql script? If
yes, can you explain
Wenkai Qi created FLINK-36636:
-
Summary: Timestamp data can not be compared in cdc pipeline
transform
Key: FLINK-36636
URL: https://issues.apache.org/jira/browse/FLINK-36636
Project: Flink
Issue
Thanks Shengakai for driving this proposal. Supporting the deployment of
sql scripts in application mode is important for improving SQL job
submission. This FLIP design looks good to me.
Best,
Junrui
Ron Liu 于2024年10月31日周四 10:20写道：
> Hi, Shengkai
>
> Thanks for your quick response. It looks goo
21 matches
Mail list logo
