Re: [DISCUSS] Support 'DYNAMIC MetadataColumn' in flink table

Your understanding is correct. In fact, my question is very simple, that is, the metadatas of the flink table is now fixed and cannot be compatible with the changes of the connector. What you said about forward compatibility and backward compatibility is very accurate, the 'DEFAULT' constraint is

Re: [ANNOUNCE] Apache Flink Table Store 0.2.0 released

Congrats! Thanks Jingsong for driving this release, and thanks to all contributors! Best, Jane On Mon, Aug 29, 2022 at 11:35 AM Jingsong Li wrote: > The Apache Flink community is very happy to announce the release of > Apache Flink Table Store 0.2.0. > > Apache Flink Table Store is a unified st

[ANNOUNCE] Apache Flink Table Store 0.2.0 released

The Apache Flink community is very happy to announce the release of Apache Flink Table Store 0.2.0. Apache Flink Table Store is a unified storage to build dynamic tables for both streaming and batch processing in Flink, supporting high-speed data ingestion and timely data query. Please check out

RE: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

> +1, this will make external systems connected to Flink more efficient. > Thanks for driving the feature. Best, Manson On 2022/08/15 10:06:18 zhengyu chen wrote: > Hi all, > > > We would like to start a discussion thread on FLIP-256 Support Job Dynamic > Parameter With Flink Re

[RESULT][VOTE] Apache Flink Table Store 0.2.0, release candidate #3

I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 3 of which are binding: * Nicholas Jiang (non-binding) * Yu Li (binding) * Jark Wu (binding) * Jane Chan (non-binding) * Jingsong Lee (binding) There are no disapproving votes. Thank you for verify

Re: [VOTE] Apache Flink Table Store 0.2.0, release candidate #3

Thanks everyone, We have 3 binding and 2 non-binding now. This voting was closed. Best, Jingsong On Mon, Aug 29, 2022 at 10:01 AM Jingsong Li wrote: > > +1 (binding) > > - check the source code > - check the signatures and sums > - run the quick start > > Best, > Jingsong > > On Sun, Aug 28, 2

Re: [VOTE] Apache Flink Table Store 0.2.0, release candidate #3

+1 (binding) - check the source code - check the signatures and sums - run the quick start Best, Jingsong On Sun, Aug 28, 2022 at 10:22 AM Jane Chan wrote: > > Hi all, > > +1 for the release (non-binding). > > - Verify that the source distributions do not contain any binaries; > - Build

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

Hi Hong: I compared @gyula and yours solutions, here are some of my thoughts: We can't control whether the user defines some parameters in the code, so I think User Code is always bigger than other configuration items (usually code in development has the highest priority) such as @gyula said, I t

[jira] [Created] (FLINK-29127) upgrade to chill java to 0.11.0 and kryo-shaded to 4.0.2

Bo Cui created FLINK-29127: -- Summary: upgrade to chill java to 0.11.0 and kryo-shaded to 4.0.2 Key: FLINK-29127 URL: https://issues.apache.org/jira/browse/FLINK-29127 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-29126) Fix spliting file optimization doesn't work for orc foramt

luoyuxia created FLINK-29126: Summary: Fix spliting file optimization doesn't work for orc foramt Key: FLINK-29126 URL: https://issues.apache.org/jira/browse/FLINK-29126 Project: Flink Issue Type

Rescuing Queryable State from deprecation

Hi - For those of you who didn’t see my talk from Flink Forward, here’s a link to the slides. By implementing the ideas first brought forward in the blog post

[jira] [Created] (FLINK-29125) Placeholder in Apache Flink Web Frontend to display some "tags" to distinguish between frontends of different clusters

Durga Krovi created FLINK-29125: --- Summary: Placeholder in Apache Flink Web Frontend to display some "tags" to distinguish between frontends of different clusters Key: FLINK-29125 URL: https://issues.apache.org/jira/

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

Originally I assumed that user code programmatic config changes always have highest priority in Flink. If I understand correctly this is true in other deployment modes . So I wouldn’t change that with a flag, the question is whether cluster config or rest api config has a higher priority. I think