Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating Hive dialect

Thanks Yuxia for driving this work. +1(binding) Best, Leonard > 2022年4月28日 下午8:29，Jing Zhang 写道： > > +1 (binding) > > Best, > Jing Zhang > > Martijn Visser 于2022年4月28日周四 20:11写道： > >> +1 (Binding) >> >> On Thu, 28 Apr 2022 at 13:40, ron wrote: >> >>> +1 >>> >>> Best, >>> Ron >>> >>>

Re: Add a init-file option into FLIP-91

Hi. LuNing. Thanks for your attention. I have responded in the discussion mails. Best, Shengkai LuNing Wang 于2022年4月27日周三 17:29写道： > Hi all, > > After I read FLIP-91[1], I want to add an init-file option. Its > functionality is the same as option '-i' of Flink SQL Client. > > When I use

Re: [DISCUSS] FLIP-223: Support HiveServer2 Endpoint

Hi, Jark and Martijn Thanks for your feedback. > Kyuubi provides three ways to configure Hive metastore [1]. Could we provide similar abilities? Yes. I have updated the FLIP about this and it takes some time to figure out how the jdbc driver works. I added the section about how to use the hive

Re: [DISCUSS] Planning Flink 1.16

+1 for a 5 months release cycle. +1 target the feature freeze date 1.5 months before the release date. It can better guard the release date. Therefore, also +1 for mid August as the feature freeze date of 1.16 Thanks, Zhu Jark Wu 于2022年4月28日周四 22:24写道： > I'm also fine with the end of July for

Re: [DISCUSS] FLIP-91: Support SQL Client Gateway

Hi Marijn and LuNing. Thanks for your feedback! > The FLIP is called "SQL Client Gateway", but isn't this a REST Gateway which would be used by Flink's SQL Client (or other applications)? Agreed. The FLIP mainly focus on the Gateway. I think it's better to rename the name to the "Support SQL

[VOTE] Apache Flink Table Store 0.1.0, release candidate #2

Hi everyone, Please review and vote on the release candidate #2 for the version 0.1.0 of Apache Flink Table Store, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) **Release Overview** As an overview, the release consists of the

Re: Failed Unit Test on Master Branch

Hi Haizhou I ran the test and there is no problem. And commit is "d940af688be90c92ce4f8b9ca883f6753c94aa0f" Best, Guowei On Fri, Apr 29, 2022 at 5:39 AM Haizhou Zhao wrote: > Hello Flink Community, > > I was encountering some unit test failure in the flink-avro sub-module when > I tried to

[jira] [Created] (FLINK-27449) The comment is lost when printing table schema

Yuan Huang created FLINK-27449: --- Summary: The comment is lost when printing table schema Key: FLINK-27449 URL: https://issues.apache.org/jira/browse/FLINK-27449 Project: Flink Issue Type: Bug

Failed Unit Test on Master Branch

Hello Flink Community, I was encountering some unit test failure in the flink-avro sub-module when I tried to pull down the master branch and build. Here is the command I ran: mvn clean package -pl flink-formats/flink-avro Here is the test that fails:

Re: [DISCUSS] FLIP-227: Support overdraft buffer

Hi, You are right about LegacySource(is the same about BoundedStreamTask?). I am not really sure about hardcoded limit. We need to think about that. Theoretically, when we create a task we know should it use overdraft or not but I am not really sure how we can use this knoweledge yet.

[jira] [Created] (FLINK-27447) Implement last-state with ZooKeeper HA

Usamah Jassat created FLINK-27447: - Summary: Implement last-state with ZooKeeper HA Key: FLINK-27447 URL: https://issues.apache.org/jira/browse/FLINK-27447 Project: Flink Issue Type:

[jira] [Created] (FLINK-27448) Enable standalone mode for old Flink versions

Usamah Jassat created FLINK-27448: - Summary: Enable standalone mode for old Flink versions Key: FLINK-27448 URL: https://issues.apache.org/jira/browse/FLINK-27448 Project: Flink Issue Type:

[jira] [Created] (FLINK-27445) Create Flink Standalone Service

Usamah Jassat created FLINK-27445: - Summary: Create Flink Standalone Service Key: FLINK-27445 URL: https://issues.apache.org/jira/browse/FLINK-27445 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27446) Introduce Standalone Mode

Usamah Jassat created FLINK-27446: - Summary: Introduce Standalone Mode Key: FLINK-27446 URL: https://issues.apache.org/jira/browse/FLINK-27446 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27444) Create standalone mode ClusterDescriptor

Usamah Jassat created FLINK-27444: - Summary: Create standalone mode ClusterDescriptor Key: FLINK-27444 URL: https://issues.apache.org/jira/browse/FLINK-27444 Project: Flink Issue Type:

[jira] [Created] (FLINK-27443) Add standalone mode parameters and decorators

Usamah Jassat created FLINK-27443: - Summary: Add standalone mode parameters and decorators Key: FLINK-27443 URL: https://issues.apache.org/jira/browse/FLINK-27443 Project: Flink Issue Type:

Re: [DISCUSS] Planning Flink 1.16

I'm also fine with the end of July for the feature freeze. Best, Jark On Thu, 28 Apr 2022 at 21:00, Martijn Visser wrote: > +1 for continuing to strive for a 5 months release cycle. > > And +1 to have the planned feature freeze mid August, which I would propose > to have happen on Monday the

[jira] [Created] (FLINK-27442) Module flink-sql-avro-confluent-registry does not configure Confluent repo

Nicolaus Weidner created FLINK-27442: Summary: Module flink-sql-avro-confluent-registry does not configure Confluent repo Key: FLINK-27442 URL: https://issues.apache.org/jira/browse/FLINK-27442

Re: [DISCUSS] Keep the Community Member Information Up-to-Date

Hi Xintong, Thanks for starting this discussion. +0 to replace the information with link to https://projects.apache.org/committee.html?flink. +1 to add such a link. My opinion is that we the community doesn't have to keep the page up to date since Apache has a member page[1] that isn't up to

[jira] [Created] (FLINK-27441) Scrollbar is missing for particular UI elements (Accumulators, Backpressure, Watermarks)

Ferenc Csaky created FLINK-27441: Summary: Scrollbar is missing for particular UI elements (Accumulators, Backpressure, Watermarks) Key: FLINK-27441 URL: https://issues.apache.org/jira/browse/FLINK-27441

Re: [DISCUSS] Keep the Community Member Information Up-to-Date

> > Personally I'm tempted to just link to > https://projects.apache.org/committee.html?flink, if at all. > Despite its fashionless look, I'm thinking the same thing... Thank you~ Xintong Song On Thu, Apr 28, 2022 at 8:41 PM Jingsong Li wrote: > One value is that this page has avatars.

Re: [DISCUSS] Planning Flink 1.16

+1 for continuing to strive for a 5 months release cycle. And +1 to have the planned feature freeze mid August, which I would propose to have happen on Monday the 15th of August 2022. I would also already state that even though we know this is a holiday period, we should not extend this deadline

Re: [DISCUSS] Keep the Community Member Information Up-to-Date

One value is that this page has avatars. :-) Best, Jingsong On Thu, Apr 28, 2022 at 8:27 PM Chesnay Schepler wrote: > > Personally I'm tempted to just link to > https://projects.apache.org/committee.html?flink, if at all. > > I'm not sure overall whether this listing really provides value in

Re: [DISCUSS] Planning Flink 1.16

Thanks for the check. > Continue to strive for a 5 months release cycle and 1.5 months before to the > desired release date Sounds good to me! Best, Jingsong On Thu, Apr 28, 2022 at 7:06 PM Konstantin Knauf wrote: > > Hi everyone, > > thank you for the feedback so far. I've checked the

Re: Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating Hive dialect

+1 (binding) Best, Jing Zhang Martijn Visser 于2022年4月28日周四 20:11写道： > +1 (Binding) > > On Thu, 28 Apr 2022 at 13:40, ron wrote: > > > +1 > > > > Best, > > Ron > > > > > > > -原始邮件- > > > 发件人: "Jark Wu" > > > 发送时间: 2022-04-28 15:46:22 (星期四) > > > 收件人: dev > > > 抄送: > > > 主题: Re:

Re: [DISCUSS] Keep the Community Member Information Up-to-Date

Personally I'm tempted to just link to https://projects.apache.org/committee.html?flink, if at all. I'm not sure overall whether this listing really provides value in the first place. On 28/04/2022 13:58, Xintong Song wrote: Hi Flink Committers & PMC members, I just noticed that the list

Re: Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating Hive dialect

+1 (Binding) On Thu, 28 Apr 2022 at 13:40, ron wrote: > +1 > > Best, > Ron > > > > -原始邮件- > > 发件人: "Jark Wu" > > 发送时间: 2022-04-28 15:46:22 (星期四) > > 收件人: dev > > 抄送: > > 主题: Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for > migrating Hive dialect > > > > +1 (binding) > >

[DISCUSS] Keep the Community Member Information Up-to-Date

Hi Flink Committers & PMC members, I just noticed that the list of community members on our website [1] is quite out-of-date. According to the ASF roster [2], this project currently has 87 committers, 39 of which are PMC members. However, there's only 62 people listed on our website, and many

Re: Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating Hive dialect

+1 Best, Ron > -原始邮件- > 发件人: "Jark Wu" > 发送时间: 2022-04-28 15:46:22 (星期四) > 收件人: dev > 抄送: > 主题: Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating > Hive dialect > > +1 (binding) > > Thank Yuxia, for driving this work. > > Best, > Jark > > On Thu, 28 Apr

Re: [DISCUSS] DockerHub repository maintainers

I agree with you that doing QA for the image after the release has been finalized doesn't feel right. IIUR, that is mostly because official image PR needs 1) the binary release being deployed and propagated and 2) the corresponding git commit being specified. I'm not completely sure about this.

Re: [DISCUSS] Planning Flink 1.16

Hi everyone, thank you for the feedback so far. I've checked the length of the previous last release cycles. Up until Flink 1.14, we've actually been incredibly good at maintaining a 5 months release cycle (see below). Interestingly, the community is officially targeting a 4 months release cycle

[jira] [Created] (FLINK-27440) adds ignore-parse-errors configuration in avro format

陈磊 created FLINK-27440: -- Summary: adds ignore-parse-errors configuration in avro format Key: FLINK-27440 URL: https://issues.apache.org/jira/browse/FLINK-27440 Project: Flink Issue Type: New Feature

Re: [DISCUSS] DockerHub repository maintainers

I still think that's mostly a process issue. Of course we can be blind-sided if we do the QA for a release artifact after the release has been finalized. But that's a clearly broken process from the get-go. At the very least we should already open a PR when the RC is created to get earlier

[jira] [Created] (FLINK-27439) Fix ClassNotFoundException when using array type in table store

Caizhi Weng created FLINK-27439: --- Summary: Fix ClassNotFoundException when using array type in table store Key: FLINK-27439 URL: https://issues.apache.org/jira/browse/FLINK-27439 Project: Flink

Re: Re: [DISCUSS] FLIP-168: Speculative execution for Batch Job

Hi, zhu Many thanks to zhuzhu for initiating the FLIP discussion. Overall I think it's ok, I just have 3 small questions 1. How to judge whether the Execution Vertex belongs to a slow task. The current calculation method is: the current timestamp minus the timestamp of the execution deployment.

[jira] [Created] (FLINK-27438) SQL validation failed when constructing a map array

Wei Zhong created FLINK-27438: - Summary: SQL validation failed when constructing a map array Key: FLINK-27438 URL: https://issues.apache.org/jira/browse/FLINK-27438 Project: Flink Issue Type:

Re: [DISCUSS] DockerHub repository maintainers

I'm overall against only releasing to official-images. We started releasing to apache/flink, in addition to the official-image, in 1.12.0. That was because releasing the official-image needs approval from the DockerHub folks, which is not under control of the Flink community. For 1.12.0 there

Re: [DISCUSS] FLIP-222: Support full query lifecycle statements in SQL client

Hi Martjin, Thanks a lot for your reply! I agree that the scope may be a bit confusing, please let me clarify. The FLIP aims to add new SQL statements that are supported only in sql-client, similar to jar statements [1]. Jar statements can be parsed into jar operations, which are used only in

[DISCUSS] FLIP-218: Support SELECT clause in CREATE TABLE(CTAS)

Hi, everyone I would like to open a discussion for support select clause in CREATE TABLE(CTAS), With the development of business and the enhancement of flink sql capabilities, queries become more and more complex. Now the user needs to use the Create Table statement to create the target table

Re: Re: [DISCUSS] FLIP-168: Speculative execution for Batch Job

+1 for the feature. Mang Zhang 于2022年4月28日周四 11:36写道： > Hi zhu: > > > This sounds like a great job! Thanks for your great job. > In our company, there are already some jobs using Flink Batch, > but everyone knows that the offline cluster has a lot more load than > the online

Re: [VOTE] FLIP-216: Introduce pluggable dialect and plan for migrating Hive dialect

+1 (binding) Thank Yuxia, for driving this work. Best, Jark On Thu, 28 Apr 2022 at 11:58, Jingsong Li wrote: > +1 (Binding) > > A very good step to move forward. > > Best. > Jingsong > > On Wed, Apr 27, 2022 at 9:33 PM yuxia wrote: > > > > Hi, everyone > > > > Thanks all for attention to

[jira] [Created] (FLINK-27437) Syntax error when running tpcds test

Yao Zhang created FLINK-27437: - Summary: Syntax error when running tpcds test Key: FLINK-27437 URL: https://issues.apache.org/jira/browse/FLINK-27437 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-27436) option `properties.group.id` is not effective in kafka connector for finksql

Spongebob created FLINK-27436: - Summary: option `properties.group.id` is not effective in kafka connector for finksql Key: FLINK-27436 URL: https://issues.apache.org/jira/browse/FLINK-27436 Project:

Re: [DISCUSS] FLIP-224: Blacklist Mechanism

Hi Konstantin, Thanks for your feedback. I will response your 4 remarks: 1) Thanks for reminding me of the controversy. I think “BlockList” is good enough, and I will change it in FLIP. 2) Your suggestion for the REST API is a good idea. Based on the above, I would change REST API as

Re: [VOTE] Apache Flink Table Store 0.1.0, release candidate #1

Thanks Caizhi for the quick validation. Let's cancel this RC and wait for your fix. Best, Jingsong On Thu, Apr 28, 2022 at 2:55 PM Caizhi Weng wrote: > > Hi all! > > -1 for this release. Currently we cannot write array and map types into > table store due to this commit >

Re: [VOTE] Apache Flink Table Store 0.1.0, release candidate #1

Hi all! -1 for this release. Currently we cannot write array and map types into table store due to this commit . Run the following SQL in SQL client and an exception will be thrown: create table if not

[VOTE] Apache Flink Table Store 0.1.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 0.1.0 of Apache Flink Table Store, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) **Release Overview** As an overview, the release consists of the

Re: [DISCUSS] DockerHub repository maintainers

We could just stop releasing to apache/flink and only go for the official-images route. On 28/04/2022 07:43, Xintong Song wrote: Forgot to mention that, we have also proposed to use one shared account and limit its access to the PMC members, like what we do with the PyPI account.