Re: [VOTE] Drop Gelly

+1 On Tue, Oct 18, 2022 at 10:49 AM Dong Lin wrote: > +1 > > On Thu, Oct 13, 2022 at 4:59 AM Martijn Visser > wrote: > > > Hi everyone, > > > > I would like to open a vote for dropping Gelly, which was discussed a > long > > time ago but never put to a vote [1]. > > > > Voting will be open for

Re: [DISCUSS] FLIP-263: Improve resolving schema compatibility

Hi, Dawid. Thanks for your reply. Should we introduce the new method to the TypeSerializerSnapshot instead? You provided a valuable option, let me try to list the benefit and cost. benefit: 1. TypeSerializerSnapshot still owns the responsibility of resolving schema compatibility so

Re: [VOTE] FLIP-265 Deprecate and remove Scala API support

+1 (binding) On Mon, Oct 17, 2022 at 6:41 AM Márton Balassi wrote: > +1 (binding) > > On Mon, Oct 17, 2022 at 3:39 PM Martijn Visser > wrote: > > > Hi everyone, > > > > I'm hereby opening a vote for FLIP-265 Deprecate and remove Scala API > > support. The related discussion can be found here

[jira] [Created] (FLINK-29683) Introduce config parser for AWS BackoffStrategy

Hong Liang Teoh created FLINK-29683: --- Summary: Introduce config parser for AWS BackoffStrategy Key: FLINK-29683 URL: https://issues.apache.org/jira/browse/FLINK-29683 Project: Flink Issue

[jira] [Created] (FLINK-29682) Flaky test failure in test_finegrained_resourcemanagement

Samrat Deb created FLINK-29682: -- Summary: Flaky test failure in test_finegrained_resourcemanagement Key: FLINK-29682 URL: https://issues.apache.org/jira/browse/FLINK-29682 Project: Flink Issue

Re: SQL Gateway and SQL Client

Thank you for the response, Yuxia! Shengkai, I would like to learn more about nearest and a bit more distant plans about development of the SQL Gateway and the SQL Client. Do you have a description of the work planned or maybe can share general thoughts about the Authentication module, or

[jira] [Created] (FLINK-29681) Python side-output operator not generated in some cases

Juntao Hu created FLINK-29681: - Summary: Python side-output operator not generated in some cases Key: FLINK-29681 URL: https://issues.apache.org/jira/browse/FLINK-29681 Project: Flink Issue

Re: Re: [DISCUSS] Aligning migration test data generation

Hi Matthias, I was mainly working on the generator class to automates the process, but sorry I'm bound up with some affairs in this week. Since currently it seems generating the snapshots is a blocker for the releasing, I think one possible way to merge the current efforts are that you continue

[jira] [Created] (FLINK-29680) Create/Use Database with DatabaseName "default" fails

Prabhu Joseph created FLINK-29680: - Summary: Create/Use Database with DatabaseName "default" fails Key: FLINK-29680 URL: https://issues.apache.org/jira/browse/FLINK-29680 Project: Flink

[jira] [Created] (FLINK-29679) DESCRIBE statement shows comment

Yubin Li created FLINK-29679: Summary: DESCRIBE statement shows comment Key: FLINK-29679 URL: https://issues.apache.org/jira/browse/FLINK-29679 Project: Flink Issue Type: New Feature

Re: Re: [DISCUSS] Aligning migration test data generation

Thanks for clarifying things and providing the link to the Jira issue. I'd be curious about the state of your efforts. I'm happy to close my PR if you're saying that your approach is more reasonable or you're almost done. But we could also merge both efforts. Either way is fine with me. Best,

[jira] [Created] (FLINK-29678) Data may loss when sink bounded stream into filesystem with auto compact enabled in streaming mode

luoyuxia created FLINK-29678: Summary: Data may loss when sink bounded stream into filesystem with auto compact enabled in streaming mode Key: FLINK-29678 URL: https://issues.apache.org/jira/browse/FLINK-29678

Re: Re: [DISCUSS] Aligning migration test data generation

Hi Matthias, Very thanks for proposing the issue! Currently when releasing a new version, it is indeed required to manully generates new test data on the branch to release (namely release-1.16) for all the compatibility tests, and then pick the files back to the master branch so that the

[jira] [Created] (FLINK-29677) DROP CATALOG statement does not reset current catalog

Jane Chan created FLINK-29677: - Summary: DROP CATALOG statement does not reset current catalog Key: FLINK-29677 URL: https://issues.apache.org/jira/browse/FLINK-29677 Project: Flink Issue Type:

Re: [DISCUSS] Aligning migration test data generation

I created a draft PR to underline my proposal [1]. The PR doesn't cover all the relevant tests, yet. I'd like to get feedback from anyone who has done minor releases in the past (CC'ing Yun Gao since he did this task for Flink 1.15) before proceeding with the tests that are still not migrated

[jira] [Created] (FLINK-29676) unexpected correlate variable $cor262 in the plan

Luochg created FLINK-29676: -- Summary: unexpected correlate variable $cor262 in the plan Key: FLINK-29676 URL: https://issues.apache.org/jira/browse/FLINK-29676 Project: Flink Issue Type: Bug

Re: SplitEnumerator for Bigquery Source.

Hi Martin, Tables are partitioned on timestamp, just like Hive. It can be range partitioned too. It doesn't matter. The option number two in the first email talks about one split of each partition. Are you suggesting something different? Thanks þri., 18. okt. 2022 kl. 15:28 skrifaði Martijn

[jira] [Created] (FLINK-29675) unexpected correlate variable $cor262 in the plan

Luochg created FLINK-29675: -- Summary: unexpected correlate variable $cor262 in the plan Key: FLINK-29675 URL: https://issues.apache.org/jira/browse/FLINK-29675 Project: Flink Issue Type: Bug

Re: SplitEnumerator for Bigquery Source.

Hi Lavkesh, I'm not familiar with Big Query but when looking through the BQ API, I noticed that the `Table` resource provides both a timePartioning and a rangePartioning. [1] Couldn't you use that? Best regards, Martijn https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#Table On

Bigquery source/connector on Flink

Hi, We are trying to implement Bigquery source on Flink. I see that there is an existing JIRA but there is no progress on it. I see there is a PoC by Mat. We are also thinking of using the DynamicTable interface to implement. We can use this