[jira] [Created] (FLINK-25068) Show the maximum parallelism (number of key groups) of a job in Web UI

zlzhang0122 created FLINK-25068: --- Summary: Show the maximum parallelism (number of key groups) of a job in Web UI Key: FLINK-25068 URL: https://issues.apache.org/jira/browse/FLINK-25068 Project: Flink

[jira] [Created] (FLINK-25067) Correct the description of RocksDB's background threads

Yun Tang created FLINK-25067: Summary: Correct the description of RocksDB's background threads Key: FLINK-25067 URL: https://issues.apache.org/jira/browse/FLINK-25067 Project: Flink Issue Type:

Re: [VOTE][FLIP-195] Improve the name and structure of vertex and operator name for job

+1 (binding). Very thanks Wenlong for the proposal! Best, Yun-- Sender:Xianxun Ye Date:2021/11/24 16:49:44 Recipient:dev@flink.apache.org Theme:[VOTE][FLIP-195] Improve the name and structure of vertex and operator name for job

[jira] [Created] (FLINK-25066) Support using multi hdfs namenode to resolved dependences when submitting job to yarn

jocean.shi created FLINK-25066: -- Summary: Support using multi hdfs namenode to resolved dependences when submitting job to yarn Key: FLINK-25066 URL: https://issues.apache.org/jira/browse/FLINK-25066

[jira] [Created] (FLINK-25065) Update lookup document for mysql-connector

Gaurav Miglani created FLINK-25065: -- Summary: Update lookup document for mysql-connector Key: FLINK-25065 URL: https://issues.apache.org/jira/browse/FLINK-25065 Project: Flink Issue Type:

Re: [DISCUSS] Drop Zookeeper 3.4

I included the user ML in the thread. @users Are you still using Zookeeper 3.4? If so, were you planning to upgrade Zookeeper in the near future? I'm not sure about ZK compatibility, but we'd also upgrade Curator to 5.x, which doesn't support ookeeperK 3.4 anymore. On 25/11/2021 21:56,

Re: [DISCUSS] Deprecate Java 8 support

+1 for the deprecation and reaching out to the user ML to ask for feedback from our users. Thanks for driving this Chesnay! Cheers, Till On Thu, Nov 25, 2021 at 10:15 AM Roman Khachatryan wrote: > The situation is probably a bit different now compared to the previous > upgrade: some users

Re: [DISCUSS] Drop Zookeeper 3.4

Should we ask on the user mailing list whether anybody is still using ZooKeeper 3.4 and thus needs support for this version or can a ZooKeeper 3.5/3.6 client talk to a ZooKeeper 3.4 cluster? I would expect that not a lot of users depend on it but just to make sure that we aren't annoying a lot of

Re: [DISCUSS] FLIP-190: Support Version Upgrades for Table API & SQL Programs

Hi Timo, Thanks for putting this amazing work together, I have some considerations/questions about the FLIP: *Proposed changes #6*: Other than defining this rule of thumb, we must also make sure that compiling plans with these objects that cannot be serialized in the plan must fail hard, so

Re: [DISCUSS] PR component labeling

Hi Chesnay, It would be fine for me to have more high-over labels, like SQL, Connectors, Formats, FileSystems. Thanks, Martijn On Thu, 25 Nov 2021 at 16:33, Chesnay Schepler wrote: > @Martijn do you need all the various sublabels, or would one like SQL or > Connectors suffice? > > On

Re: [DISCUSS] PR component labeling

@Martijn do you need all the various sublabels, or would one like SQL or Connectors suffice? On 25/11/2021 16:28, Martijn Visser wrote: Hi Nico, I'm using the labels to filter on PRs that I find interesting (for example, I look at all the new or updated PRs that are related to SQL or

Re: [DISCUSS] PR component labeling

Hi Nico, I'm using the labels to filter on PRs that I find interesting (for example, I look at all the new or updated PRs that are related to SQL or connectors). Best regards, Martijn On Thu, 25 Nov 2021 at 16:17, Nicolaus Weidner < nicolaus.weid...@ververica.com> wrote: > Hi all, > > since

[DISCUSS] PR component labeling

Hi all, since we are currently working on several infrastructure topics, I would like to start a discussion on whether the component labeling on PRs is actually helping people. To be clear, I am talking about the blue labels like "component=Runtime/metrics" that are added by the omnipresent

[jira] [Created] (FLINK-25064) Remove @VisibleForTesting from RestServerEndpoint#createUploadDir

Chesnay Schepler created FLINK-25064: Summary: Remove @VisibleForTesting from RestServerEndpoint#createUploadDir Key: FLINK-25064 URL: https://issues.apache.org/jira/browse/FLINK-25064 Project:

[jira] [Created] (FLINK-25063) Allow calls to @VisibleForTesting from enclosing class

Chesnay Schepler created FLINK-25063: Summary: Allow calls to @VisibleForTesting from enclosing class Key: FLINK-25063 URL: https://issues.apache.org/jira/browse/FLINK-25063 Project: Flink

[jira] [Created] (FLINK-25062) Implement all catalog methods for PostgresCatalog

Martijn Visser created FLINK-25062: -- Summary: Implement all catalog methods for PostgresCatalog Key: FLINK-25062 URL: https://issues.apache.org/jira/browse/FLINK-25062 Project: Flink Issue

Re: [DISCUSS] Creating an external connector repository

Hi Brian, Thank you for sharing. I think your approach is very valid and is in line with what I had in mind. Basically Pravega community aligns the connector releases with the Pravega > mainline release > This certainly would mean that there is little value in coupling connector versions. So

回复: RocksDBMapState get the binary key bytes

Hi Pengfei Li: I have not encountered this in production yet, I just check the code and found this is not the same with no userkey suppilied. I checked the MapSerializer and found the serialized format for each Map.entry is [key – isValueNull(boolean) – value]. And When boolean is

Re: [DISCUSS] Conventions on assertions to use in tests

As @Matthias Pohl mentioned, I agree that no1 is to end up with consistency regarding the assertions in our tests, but I also like how those assertions shape up with the AssertJ approach. On Thu, Nov 25, 2021 at 9:38 AM Francesco Guardiani wrote: > This is the result of experimenting around

[jira] [Created] (FLINK-25061) Add assertj as dependency in flink-parent

Francesco Guardiani created FLINK-25061: --- Summary: Add assertj as dependency in flink-parent Key: FLINK-25061 URL: https://issues.apache.org/jira/browse/FLINK-25061 Project: Flink

[jira] [Created] (FLINK-25060) Replace DataType.projectFields with Projection type

Francesco Guardiani created FLINK-25060: --- Summary: Replace DataType.projectFields with Projection type Key: FLINK-25060 URL: https://issues.apache.org/jira/browse/FLINK-25060 Project: Flink

[jira] [Created] (FLINK-25059) Update code style guide to encourage usage of AssertJ

Chesnay Schepler created FLINK-25059: Summary: Update code style guide to encourage usage of AssertJ Key: FLINK-25059 URL: https://issues.apache.org/jira/browse/FLINK-25059 Project: Flink

[jira] [Created] (FLINK-25058) Declared exceptions should be considered in architectural tests

Ingo Bürk created FLINK-25058: - Summary: Declared exceptions should be considered in architectural tests Key: FLINK-25058 URL: https://issues.apache.org/jira/browse/FLINK-25058 Project: Flink

[jira] [Created] (FLINK-25057) Streaming File Sink writing to the HDFS

hanjie created FLINK-25057: -- Summary: Streaming File Sink writing to the HDFS Key: FLINK-25057 URL: https://issues.apache.org/jira/browse/FLINK-25057 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-25056) Modify Flink dashboard task manager page, "Path, ID" column，to support sorting by id.

john created FLINK-25056: Summary: Modify Flink dashboard task manager page, "Path, ID" column，to support sorting by id. Key: FLINK-25056 URL: https://issues.apache.org/jira/browse/FLINK-25056 Project: Flink

Re: RocksDBMapState get the binary key bytes

This problem is tracked in FLINK-11141 , but there is not a solution yet considering the state compatibility. Have you encountered the problem in production? Zen4YYDS 于2021年11月25日周四 下午3:30写道： > Hi devs: > > Using RocksDB, when key and

Re: [DISCUSS] Definition of Done for Apache Flink

> * 187 contain "yes / no / don't know" and thus have not answered at least one of the questions I think there are quite some PRs that highlight in bold the answer to this question while keeping all options there. I'm all in favour of replacing this with a checkbox. On Thu, 25 Nov 2021 at

Re: [DISCUSS] Definition of Done for Apache Flink

Hi Till, > * I agree with Ingo that the "Verifying this change" section can be > cumbersome to fill in. On the other hand it reminds contributors to verify > that his/her changes are covered by tests. Therefore, I would keep it. IMO it could be replaced with a checkbox "I have made sure all

Re: [DISCUSS] Definition of Done for Apache Flink

When I started writing this response I thought that the current PR template is mostly ignored by the community. In order to verify this I went through the first two pages of open PRs and I was very positively surprised that almost all PRs filled out the current template. Hence, I had to redact my

[jira] [Created] (FLINK-25055) Support listen and notify mechanism for PartitionRequest

Shammon created FLINK-25055: --- Summary: Support listen and notify mechanism for PartitionRequest Key: FLINK-25055 URL: https://issues.apache.org/jira/browse/FLINK-25055 Project: Flink Issue Type:

Re: [DISCUSS] Deprecate Java 8 support

The situation is probably a bit different now compared to the previous upgrade: some users might be using Amazon Coretto (or other builds) which have longer support. Still +1 for deprecation to trigger migration, and thanks for bringing this up! Regards, Roman On Thu, Nov 25, 2021 at 10:09 AM

Re: [DISCUSS] Deprecate Java 8 support

+1 to deprecate Java 8, so we can hopefully incorporate the module concept in Flink. On Thu, Nov 25, 2021 at 9:49 AM Chesnay Schepler wrote: > Users can already use APIs from Java 8/11. > > On 25/11/2021 09:35, Francesco Guardiani wrote: > > +1 with what both Ingo and Matthias sad, personally,

[jira] [Created] (FLINK-25054) flink sql System (Built-in) Functions 【SHA2】，hashLength validation Unsurpport

chenbowen created FLINK-25054: - Summary: flink sql System (Built-in) Functions 【SHA2】，hashLength validation Unsurpport Key: FLINK-25054 URL: https://issues.apache.org/jira/browse/FLINK-25054 Project:

[jira] [Created] (FLINK-25053) Document how to use the usrlib to load code in the user code class loader

Till Rohrmann created FLINK-25053: - Summary: Document how to use the usrlib to load code in the user code class loader Key: FLINK-25053 URL: https://issues.apache.org/jira/browse/FLINK-25053 Project:

[jira] [Created] (FLINK-25052) Port row to row cast logic to CastRule

Francesco Guardiani created FLINK-25052: --- Summary: Port row to row cast logic to CastRule Key: FLINK-25052 URL: https://issues.apache.org/jira/browse/FLINK-25052 Project: Flink Issue

[jira] [Created] (FLINK-25051) Port raw <-> binary logic to CastRule

Francesco Guardiani created FLINK-25051: --- Summary: Port raw <-> binary logic to CastRule Key: FLINK-25051 URL: https://issues.apache.org/jira/browse/FLINK-25051 Project: Flink Issue

Re: [DISCUSS] Deprecate Java 8 support

Users can already use APIs from Java 8/11. On 25/11/2021 09:35, Francesco Guardiani wrote: +1 with what both Ingo and Matthias sad, personally, I cannot wait to start using some of the APIs introduced in Java 9. And I'm pretty sure that's the same for our users as well. On Tuesday, 23

Re: [DISCUSS] Conventions on assertions to use in tests

This is the result of experimenting around creating custom assertions for Table API types https://github.com/slinkydeveloper/flink/commit/ d1ce37a62c2200b2c3008a9cc2cac91234222fd5[1]. I will PR it once the two PRs in the previous mail get merged On Monday, 22 November 2021 17:59:29 CET

Re: [DISCUSS] Deprecate Java 8 support

+1 with what both Ingo and Matthias sad, personally, I cannot wait to start using some of the APIs introduced in Java 9. And I'm pretty sure that's the same for our users as well. On Tuesday, 23 November 2021 13:35:07 CET Ingo Bürk wrote: > Hi everyone, > > continued support for Java 8 can

Re: [DISCUSS] Releasing Flink 1.14.1

Hey Martijn, +1 for releasing 1.14.1 As for https://issues.apache.org/jira/browse/FLINK-24328 I removed the 1.14.1 fix version. It definitely should not block the release. If we decide to backport it to 1.14.x it can safely land in 1.14.2. Best, Dawid On 24/11/2021 19:40, Martijn Visser