[RESULT][VOTE] FLIP-496: SQL connector for keyed state data

Hi All, I'm glad to announce that the FLIP-496: SQL connector for keyed state data[1] has been accepted. The voting thread is here[2]. The proposal received 4 approving votes, 4 of which are binding: - Zakelly Lan (binding) - Marton Balassi (binding) - Ferenc Csaky (binding) - Gabor So

Re: [VOTE] FLIP-496: SQL connector for keyed state data

t; > balassi.mar...@gmail.com> wrote: > > > > > > > +1 (binding) > > > > Thanks, G. > > > > On Thu, Jan 9, 2025 at 4:17 PM Zakelly Lan zakelly@gmail.com wrote: > > > > > +1 (binding) > > > > > > Thanks for driving

[VOTE] FLIP-496: SQL connector for keyed state data

Hi All, I'd like to start a vote of FLIP-496: SQL connector for keyed state data [1]. The discussion thread can be found here [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-496%3A+SQL+c

Re: Full Checkpoint information in UI and API

Hi Ryan, +1 for the name "incremental". Just had a look at the PR and looks like it has a compile error [1]. Additionally if it's possible it would be good to add some automated test. [1] https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=64974&view=logs&j=52b61abe-a3cc-5bde-c

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

s my understanding > correct? > > Regards > Venkata krishnan > > > On Mon, Dec 23, 2024 at 6:59 PM Shengkai Fang wrote: > > > Thanks for your clarification. Looking forward to the following FLIPs. > > > > Best, > > Shengkai > > > > Ga

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

ate and uses state > descriptor to restore the schema. > 2. Can the connector provide more metadata information for users? For > example, the `ttl` field is very useful in our cases. > > Best, > Shengkai > > > > > Gabor Somogyi 于2024年12月19日周四 21:41写道： > > &

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

ors/SourceOperator.java#L109 > [2] > https://github.com/apache/flink/blob/9e38f32889e097f5a9b81f949643a2b037c1035c/flink-core/src/main/java/org/apache/flink/core/io/SimpleVersionedSerializer.java#L50 > > > > > > > 2024年12月18日 17:43，Gabor Somogyi 写道： > > > > Hi Al

Re: Java truststores

> > -- > > Nic Townsend > IBM Event Processing > Senior Engineer / Technical Lead > > Slack: @nictownsend > > > > From: Gabor Somogyi > Date: Thursday, 19 December 2024 at 11:07 > To: dev@flink.apache.org > Subject: [EXTERNAL] Re: Java truststores > Hi N

Re: Java truststores

Hi Nic, Not sure I understand all of the road blockers but truststore is normally not per application but per company/org which is relatively static (or at least not short lived). Keystores are normally propagated through volume mounts. Is it not possible to import the truststore into the JVM tr

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

Agreed, making the adjustments in the FLIP... On Thu, Dec 19, 2024 at 11:33 AM Zakelly Lan wrote: > Hi Gabor, > > Yes, that's what I meant. > > > Best, > Zakelly > > On Thu, Dec 19, 2024 at 6:22 PM Gabor Somogyi > wrote: > > > Hi Zakelly, >

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

ator-state > > Best, > Zakelly > > On Thu, Dec 19, 2024 at 4:46 PM Gabor Somogyi > wrote: > > > Hi Zakelly, > > > > Fair point to have short names. > > How about having the following configs then? > > > > connector=savepoint > > state.t

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

r each type of state. For the second option it means the current > connector will be named 'savepoint-keyed'? Well I slightly prefer a short > name. > > For connector='metadata', it seems unclear to me (what is metadata of Flink > :D), so I don't recommend

Re: [DISCUSS] FLIP-496: SQL connector for keyed state data

r deep consideration I would say no, but I'm going to think it through. >4. I'm not sure if the general option 'key.format' is needed, would >using 'fields.k.format' while the 'k' is the name of the SQL primary > column >be feasible? > I

Re: [VOTE] FLIP-488: Expose Async State Processing and New State APIs in Datastream(V1) APIs

+1 (binding) BR, G On Wed, Dec 18, 2024 at 10:17 AM Yunfeng Zhou wrote: > +1(non-binding) > > Best, > Yunfeng > > > 2024年12月17日 12:17，Zakelly Lan 写道： > > > > Hi all, > > > > I'd like to start a vote on FLIP-488 [1], which has been discussed here > [2]. > > > > The vote will remain open for at

[DISCUSS] FLIP-496: SQL connector for keyed state data

Hi All, I'd like to start a discussion of FLIP-496: SQL connector for keyed state data [1]. Feel free to add your thoughts to make this feature better. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-496%3A+SQL+connector+for+keyed+state+data BR, G

[jira] [Created] (FLINK-36929) SQL connector for keyed state data

Gabor Somogyi created FLINK-36929: - Summary: SQL connector for keyed state data Key: FLINK-36929 URL: https://issues.apache.org/jira/browse/FLINK-36929 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-36856) CollectSinkOperatorFactory is not respecting batch size and socket timeout configs

Gabor Somogyi created FLINK-36856: - Summary: CollectSinkOperatorFactory is not respecting batch size and socket timeout configs Key: FLINK-36856 URL: https://issues.apache.org/jira/browse/FLINK-36856

Re: Flink V1 to V2 state migration

Hi David, I think the first task would be to test and collect what is not working when migrating from 1.20 to 2.0-preview. To see such issues in advance would be really awesome, since it would ease the fixing/adaptation. When we have such list we can discuss how severe are they and how to address

Re: Micro batching with flink

Presume you're coming from Spark and looking for something like RDD.foreach. In Flink there is no such feature. I think you can use a batch job for processing and storing the data. All the rest can be done in a custom code outside of Flink. The hard way is to implement a custom connector which is

Re: Major performance degradation in case of list operator state restore from S3

Just for the record, this conversation continued and resolved in user list [1] and in the PR [2]. [1] https://lists.apache.org/thread/h5mv6ld4l2g4hsjszfdos9f365nh7ctf [2] https://github.com/apache/flink/pull/25509 G On Tue, Oct 15, 2024 at 4:26 PM Gabor Somogyi wrote: > Hi All, >

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.10.0, release candidate #1

+1 (non-binding) * Verified versions in the poms * Built from source * Verified checksums and signatures * Started basic workload * Verified NOTICE and LICENSE files G On Fri, Oct 18, 2024 at 4:45 AM Sam Barker wrote: > +1 (non binding) > > I've verified: > - The src tarball builds and passes

Major performance degradation in case of list operator state restore from S3

Hi All, As a result of our investigation we've found major performance degradation described here [1]. TLDR: list operator state restore from S3 is significantly slower from 1.18.2. Both uncompressed and compressed state is effected. ~6Mb restore takes ~62 hours. We've created already a solution

[jira] [Created] (FLINK-36530) Not able to restore list state from S3

Gabor Somogyi created FLINK-36530: - Summary: Not able to restore list state from S3 Key: FLINK-36530 URL: https://issues.apache.org/jira/browse/FLINK-36530 Project: Flink Issue Type: Bug

Re: [VOTE] FLIP-349: Move RocksDB statebackend classes to o.a.f.state.rocksdb package

+1 (binding) G On Mon, Oct 7, 2024 at 6:20 PM Zakelly Lan wrote: > Hi everyone, > > I'd like to start a vote on FLIP-349: Move RocksDB statebackend classes to > o.a.f.state.rocksdb package [1]. The discussion can be found here [2]. > > The vote will be open for at least 72 hours unless there a

Re: Flink Slack invite

ng Slack member can also invite anyone else to join.” > > Could you please provide a working invite link? > > Thank you, > Ralph > > From: Gabor Somogyi > Date: Friday, 4 October 2024 at 11:12 > To: dev@flink.apache.org > Subject: Re: Flink Slack invite > > E

Re: Flink Slack invite

Hi Hiya, You can find the description here: https://flink.apache.org/what-is-flink/community/#slack G On Fri, Oct 4, 2024 at 10:51 AM Ralph Bartley wrote: > Hiya, > > I would like to join the Flink Slack community, could someone send me an > invite link please? > > Thank you, > Ralph Bartley

Re: [DISCUSS][2.0] FLIP-349: Move RocksDB statebackend classes to o.a.f.state.rocksdb package

I personally don't see any open questions so we can proceed. G On Sun, Sep 29, 2024 at 1:43 PM Zakelly Lan wrote: > Hi everyone, > > I'd like to help move this forward. Based on our previous discussion, I > will proceed with a vote in the coming days if there are no objections. > > > Best, > Z

Re: [DISCUSSION] Disabling japicmp plugin in master for 2.0

Hi Matthias, I would turn japicmp for 2.0 off because adding a long list of exceptions doesn't give any value. 1.x and 2.x is not going to be compatible in any way and when 2.x released, then that will be the new japicmp baseline (after a heavy migration). What I see as a potential risk it that w

[RESULT][VOTE] FLIP-474: Store operator name and UID in state metadata

Hi All, I'm glad to announce that FLIP-474[1] has been accepted. There are 9 approving votes, 7 of which are binding: - Marton Balassi (binding) - Ferenc Csaky (binding) - Gyula Fora (binding) - Orhidi Matyas (binding) - Peter Huang (non-binding) - Clara Xiong (non-binding) - Zakelly Lan (binding

[jira] [Created] (FLINK-36173) Invalid link in checkpoint documentation

Gabor Somogyi created FLINK-36173: - Summary: Invalid link in checkpoint documentation Key: FLINK-36173 URL: https://issues.apache.org/jira/browse/FLINK-36173 Project: Flink Issue Type: Bug

[VOTE] FLIP-474: Store operator name and UID in state metadata

Hi All, I would like to start a vote on FLIP-474: Store operator name and UID in state metadata [1]. The discussion thread can be found here [2]. During the discussion a clear need formed to have an umbrella document about the global view which manifested in Flink state observability umbrella [3]

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

Hi All, Thanks for the contributions! The asked umbrella document helped to resolve all the misunderstandings and align to a common result. As a result I think we're ready for the voting thread. BR, G On Mon, Aug 19, 2024 at 8:47 AM Gabor Somogyi wrote: > Hi All, > > Based on

Re: [jira](FLINK-35444) Apply for a jira account and repair bug

Hi, I think you can file PR wihout jira access. Once the PR is there we can handle the rest. Please read through the contribution guide [1], which can give you good corner points. [1] https://flink.apache.org/how-to-contribute/contribute-code/ BR, G On Thu, Aug 22, 2024 at 10:06 AM 郑恺原 wrote:

[jira] [Created] (FLINK-36124) S3RecoverableFsDataOutputStream.sync closes the stream and further write operation throw exception

Gabor Somogyi created FLINK-36124: - Summary: S3RecoverableFsDataOutputStream.sync closes the stream and further write operation throw exception Key: FLINK-36124 URL: https://issues.apache.org/jira/browse/FLINK

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

observability approach. These considerations > deserve a discussion before proceeding with other details. WDTY? > > > Best, > Zakelly > > On Fri, Aug 9, 2024 at 8:22 PM Gabor Somogyi > wrote: > > > Hi David, > > > > Thanks for sharing your thoughts! >

Re: Rebuilding flink

Flink does, but maven not always detect the changes for god knows why. Gradle is slightly better but also not flawless. So for testing it may work, but for releases I suggest not to use. G On Sat, Aug 10, 2024, 00:17 Dan Plyukhin wrote: > Does Flink support incremental builds? I just started ha

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

gt; a core principle of community-driven open-source development. > > Would it be too much to ask for a FLIP that outlines the overall vision > (without delving too deeply into the details) to ensure everyone is aligned > and moving in the same direction? > > Best, > D.

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

clicking and > zooming in on the operator you want to query. IIUC, this hash can be used > to query the state. Is this feasible? Additionally, I think we could add > user-defined UIDs on the web UI and related REST APIs. Thus users could > easily identify an operator by uid, or

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

details about the > issue you are facing? > > Regarding the checkpoint, it is not designed to be self-contained or > human-readable. I suggest not introducing such columns for debugging > purposes. > > > Best, > Zakelly > > On Wed, Aug 7, 2024 at 10:07 PM Gabor Somogyi &

[DISCUSS] FLIP-474: Store operator name and UID in state metadata

Hi Devs, I would like to start a discussion on FLIP-474: Store operator name and UID in state metadata[1]. In short users are interested in what kind of operators are inside a checkpoint data which can be enhanced from user experience perspective. The details can be found in FLIP-474[1]. Please

[jira] [Created] (FLINK-36001) Store operator name and UID in state metadata

Gabor Somogyi created FLINK-36001: - Summary: Store operator name and UID in state metadata Key: FLINK-36001 URL: https://issues.apache.org/jira/browse/FLINK-36001 Project: Flink Issue Type

Re: [DISCUSS] Remove deprecated dataset based API from State Processor API

Thanks for the feedbacks, since no objection proceeding. G On Thu, Aug 1, 2024 at 2:06 PM Gabor Somogyi wrote: > Hi Ferenc, > > That's a good point! Let's wait for Monday for further opinions. > > BR, > G > > > On Thu, Aug 1, 2024 at 12:55 PM Ferenc Csak

[jira] [Created] (FLINK-35969) Remove deprecated dataset based API from State Processor API

Gabor Somogyi created FLINK-35969: - Summary: Remove deprecated dataset based API from State Processor API Key: FLINK-35969 URL: https://issues.apache.org/jira/browse/FLINK-35969 Project: Flink

Re: [DISCUSS] Remove deprecated dataset based API from State Processor API

moving the DataSet based APIs from the state processor in the > next > > Flink version, I don't think we should wait until 2.0. > > This will also reduce the 2.0 scope overall which is always good :) > > > > Cheers, > > Gyula > > > > On Wed, Ju

[DISCUSS] Remove deprecated dataset based API from State Processor API

Hi Devs, There is a common agreement that the dataset API going to be removed in 2.0. We're planning to invest quite some time in the State Processor API[1] in the near future. On this road we've realized that there are several deprecated APIs in this area which are based on the dataset API (for

Re: [VOTE] FLIP-461: Synchronize rescaling with checkpoint creation to minimize reprocessing for the AdaptiveScheduler

+1 (binding) G On Mon, Jun 17, 2024 at 10:24 AM Matthias Pohl wrote: > Hi everyone, > the discussion in [1] about FLIP-461 [2] is kind of concluded. I am > starting a vote on this one here. > > The vote will be open for at least 72 hours (i.e. until June 20, 2024; > 8:30am UTC) unless there ar

Re: [VOTE] FLIP-464: Merge "flink run" and "flink run-application"

+1 (binding) G On Wed, Jun 12, 2024 at 5:23 PM Ferenc Csaky wrote: > Hello devs, > > I would like to start a vote about FLIP-464 [1]. The FLIP is about to > merge back the > "flink run-application" functionality to "flink run", so the latter will > be capable to deploy jobs in > all deployment

Re: [VOTE] FLIP-447: Upgrade FRocksDB from 6.20.3 to 8.10.0

+1 (binding) This will be a good addition. G On Mon, May 6, 2024 at 4:54 AM yue ma wrote: > Hi everyone, > > Thanks for all the feedback, I'd like to start a vote on the FLIP-447: > Upgrade FRocksDB from 6.20.3 to 8.10.0 [1]. The discussion thread is here > [2]. > > The vote will be open for

Re: [VOTE] FLIP-439: Externalize Kudu Connector from Bahir

+1 (binding) G On Wed, Mar 20, 2024 at 3:59 PM Gyula Fóra wrote: > +1 (binding) > > Thanks! > Gyula > > On Wed, Mar 20, 2024 at 3:36 PM Mate Czagany wrote: > > > +1 (non-binding) > > > > Thank you, > > Mate > > > > Ferenc Csaky ezt írta (időpont: 2024. márc. > > 20., Sze, 15:11): > > > > > H

[jira] [Created] (FLINK-34574) Add CPU and memory size autoscaler quota

Gabor Somogyi created FLINK-34574: - Summary: Add CPU and memory size autoscaler quota Key: FLINK-34574 URL: https://issues.apache.org/jira/browse/FLINK-34574 Project: Flink Issue Type: New

[jira] [Created] (FLINK-34198) Remove e2e test operator log error check

Gabor Somogyi created FLINK-34198: - Summary: Remove e2e test operator log error check Key: FLINK-34198 URL: https://issues.apache.org/jira/browse/FLINK-34198 Project: Flink Issue Type

Re: [VOTE] FLIP-372: Allow TwoPhaseCommittingSink WithPreCommitTopology to alter the type of the Committable

+1 (binding) G On Mon, Dec 18, 2023 at 9:34 AM Péter Váry wrote: > Hi everyone, > > Since there were no further comments on the discussion thread [1], I would > like to start the vote for FLIP-372 [2]. > > The FLIP started as a small new feature, but in the discussion thread and > in a similar

[RESULT][VOTE] FLIP-401: REST API JSON response deserialization unknown field tolerance

Hi All, FLIP-401: REST API JSON response deserialization unknown field tolerance [1] has been accepted and voted through this thread [2]. The proposal received 4 binding approval votes and there is no disapproval: - Gyula Fora (binding) - Mátyás Őrhidi (binding) - Peter Huang (non-binding) - Maxi

Re: [DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

Gyula Fóra wrote: > > > Thanks Gabor! > > > > +1 from my side, this sounds like a reasonable change that will > > improve integration and backward compatibility. > > > > Let's keep this open for at least another day before starting the vote. > >

[VOTE] FLIP-401: REST API JSON response deserialization unknown field tolerance

Hi All, I'd like to start a vote on FLIP-401: REST API JSON response deserialization unknown field tolerance [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. BR, G [1] https://cwiki.apache.org/confluen

[DISCUSS] FLIP-401: REST API JSON response deserialization unknown field tolerance

Hi All, I'd like to start a discussion of FLIP-401: REST API JSON response deserialization unknown field tolerance[1]. *Problem statement:* At the moment Flink is not ignoring unknown fields when parsing REST responses. An example for such a class is *JobDetailsInfo* but this applies to all othe

Re: [DISCUSS] REST API response parsing throws exception on new fields

Switching to the new thread... G On Thu, Dec 7, 2023 at 10:25 AM Gyula Fóra wrote: > You should start a new discussion thread according to the FLIP guidelines, > so that it's identifiable that this is a FLIP discussion. > > Gyula > > On Thu, Dec 7, 2023 at 10:22 AM

Re: [DISCUSS] REST API response parsing throws exception on new fields

gt; this probably warrants a FLIP and a proper vote. > > Cheers, > Gyula > > On Wed, Dec 6, 2023 at 10:53 AM Gabor Somogyi > wrote: > > > Hi All, > > > > Since the possible solution can have effect on all the REST response > > deserialization I would

[DISCUSS] REST API response parsing throws exception on new fields

Hi All, Since the possible solution can have effect on all the REST response deserialization I would like ask for opinions. *Problem statement:* At the moment Flink is not ignoring unknown fields when parsing REST responses. An example for such a class is JobDetailsInfo but this applies to all o

Re: Python connector question

Hi Peter, Thanks for picking this up! Please find my thoughts inline. BR, G On Mon, Nov 27, 2023 at 4:05 PM Péter Váry wrote: > Hi Team, > > During some, mostly unrelated work we come to realize that during the > externalization of the connector's python modules and the related tests are > no

[jira] [Created] (FLINK-33515) PythonDriver need to stream python process output to log instead of collecting it in memory

Gabor Somogyi created FLINK-33515: - Summary: PythonDriver need to stream python process output to log instead of collecting it in memory Key: FLINK-33515 URL: https://issues.apache.org/jira/browse/FLINK-33515

Re: [VOTE] FLIP-371: Provide initialization context for Committer creation in TwoPhaseCommittingSink

+1 (binding) On Mon, Oct 16, 2023 at 12:20 PM Péter Váry wrote: > Any more comments? > > Leonard Xu ezt írta (időpont: 2023. okt. 16., H, > 8:22): > >> Thanks Peter for driving this work. >> >> >> +1(binding) >> >> Best, >> Leonard >> >> > 2023年10月12日 下午10:58，Márton Balassi 写道： >> > >> > +1 (b

[jira] [Created] (FLINK-33268) Flink REST API response parsing should support backward compatible changes like new fields

Gabor Somogyi created FLINK-33268: - Summary: Flink REST API response parsing should support backward compatible changes like new fields Key: FLINK-33268 URL: https://issues.apache.org/jira/browse/FLINK-33268

Re: [DISCUSS] FLIP-371: SinkV2 Committer imporvements

Thanks for the efforts Peter! I've just analyzed it through and I think it's useful feature. +1 from my side. G On Thu, Oct 5, 2023 at 12:35 PM Péter Váry wrote: > For the record, after the rename, the new FLIP link is: > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-371%3A+Provid

[jira] [Created] (FLINK-33172) Bump numpy version

Gabor Somogyi created FLINK-33172: - Summary: Bump numpy version Key: FLINK-33172 URL: https://issues.apache.org/jira/browse/FLINK-33172 Project: Flink Issue Type: Improvement

Re: [ANNOUNCE] Release 1.18.0, release candidate #1

Thanks for the efforts! +1 (non-binding) * Verified versions in the poms * Built from source * Verified checksums and signatures * Started basic workloads with kubernetes operator * Verified NOTICE and LICENSE files G On Fri, Sep 29, 2023, 18:16 Matthias Pohl wrote: > Thanks for creating RC1.

[jira] [Created] (FLINK-33108) Error during error status handling

Gabor Somogyi created FLINK-33108: - Summary: Error during error status handling Key: FLINK-33108 URL: https://issues.apache.org/jira/browse/FLINK-33108 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-33105) Evaluate operator log entry: Exception while fetching cluster info

Gabor Somogyi created FLINK-33105: - Summary: Evaluate operator log entry: Exception while fetching cluster info Key: FLINK-33105 URL: https://issues.apache.org/jira/browse/FLINK-33105 Project: Flink

Re: [DISCUSS] Drop python 3.7 support in 1.19

53 AM Gabor Somogyi wrote: > Hi Xingbo, > > Thanks for your support! > > I agree that multi-platform in general is a good idea. We start with ARM > but this opens the door for all others. > > G > > > On Wed, Sep 6, 2023 at 10:46 AM Xingbo Huang wrote: > >>

Re: How to test "Build snapshot binary release" nightly job against a PR

pache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml > > On Thu, Sep 7, 2023 at 10:54 AM Gabor Somogyi > wrote: > > > Hi All, > > > > I've created a PR <https://github.com/apache/flink/pull/23359> which > > changes "tools/releasing

How to test "Build snapshot binary release" nightly job against a PR

Hi All, I've created a PR which changes "tools/releasing/create_binary_release.sh" which is called by "Build snapshot binary release" nightly job. Is there a possibility to double check that the PR is not breaking it? The question can be generalized ho

Re: [DISCUSS] Drop python 3.7 support in 1.19

1 for drop 3.7 support in 1.19 > > [1] https://github.com/actions/runner-images/issues/2187 > [2] https://github.com/github/roadmap/issues/528 > > Best, > Xingbo > > Gabor Somogyi 于2023年9月6日周三 16:07写道： > > > Hi Xingbo, > > > > > So I guess you want to r

Re: [DISCUSS] Drop python 3.7 support in 1.19

onment, but the current version of miniconda cannot meet this > requirement, so there is a pre-step that must drop python 3.7? > > [1] https://pypi.org/project/apache-flink/1.16.2/#files > [2] > > https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-python-wheels.yml#

Re: [DISCUSS] Drop python 3.7 support in 1.19

> > [2] https://issues.apache.org/jira/browse/FLINK-28195 > > [3] https://issues.apache.org/jira/browse/FLINK-27929 > > > > Best, > > Xingbo > > > > Jing Ge 于2023年9月5日周二 04:10写道： > > > > > +1 > > > > > > @Dian sho

Re: [DISCUSS] Drop python 3.7 support in 1.19

d added 3.10) in Flink 1.17 [1,2], it makes sense > to > > > > proceed to remove 3.7 and add 3.11 instead. > > > > > > > > +1. > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-27929 > > > > [2] https://github.

[jira] [Created] (FLINK-33030) Add python 3.11 support

Gabor Somogyi created FLINK-33030: - Summary: Add python 3.11 support Key: FLINK-33030 URL: https://issues.apache.org/jira/browse/FLINK-33030 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-33029) Drop python 3.7 support

Gabor Somogyi created FLINK-33029: - Summary: Drop python 3.7 support Key: FLINK-33029 URL: https://issues.apache.org/jira/browse/FLINK-33029 Project: Flink Issue Type: New Feature

[DISCUSS] Drop python 3.7 support in 1.19

Hi All, I've analyzed through part of the pyflink code and found some improvement possibilities. I would like to hear voices on the idea. Intention: * upgrade several python related versions to eliminate end-of-life issues and keep up with bugfixes * start to add python arm64 support Actual situ

[jira] [Created] (FLINK-32981) Add python dynamic Flink home detection

Gabor Somogyi created FLINK-32981: - Summary: Add python dynamic Flink home detection Key: FLINK-32981 URL: https://issues.apache.org/jira/browse/FLINK-32981 Project: Flink Issue Type

[jira] [Created] (FLINK-32971) Add pyflink proper development version support

Gabor Somogyi created FLINK-32971: - Summary: Add pyflink proper development version support Key: FLINK-32971 URL: https://issues.apache.org/jira/browse/FLINK-32971 Project: Flink Issue Type

[jira] [Created] (FLINK-32465) KerberosLoginProvider.isLoginPossible does accidental login with keytab

Gabor Somogyi created FLINK-32465: - Summary: KerberosLoginProvider.isLoginPossible does accidental login with keytab Key: FLINK-32465 URL: https://issues.apache.org/jira/browse/FLINK-32465 Project

[jira] [Created] (FLINK-32415) Add maven wrapper to benchmark to avoid maven version issues

Gabor Somogyi created FLINK-32415: - Summary: Add maven wrapper to benchmark to avoid maven version issues Key: FLINK-32415 URL: https://issues.apache.org/jira/browse/FLINK-32415 Project: Flink

[jira] [Created] (FLINK-31839) It's not possible to add flink-s3-fs-hadoop and flink-s3-fs-presto plugins at the same time

Gabor Somogyi created FLINK-31839: - Summary: It's not possible to add flink-s3-fs-hadoop and flink-s3-fs-presto plugins at the same time Key: FLINK-31839 URL: https://issues.apache.org/jira/browse/FLINK-

[jira] [Created] (FLINK-31656) Obtain delegation tokens early to support external file system usage in blob server

Gabor Somogyi created FLINK-31656: - Summary: Obtain delegation tokens early to support external file system usage in blob server Key: FLINK-31656 URL: https://issues.apache.org/jira/browse/FLINK-31656

[jira] [Created] (FLINK-31284) Increase KerberosLoginProvider test coverage

Gabor Somogyi created FLINK-31284: - Summary: Increase KerberosLoginProvider test coverage Key: FLINK-31284 URL: https://issues.apache.org/jira/browse/FLINK-31284 Project: Flink Issue Type

[jira] [Created] (FLINK-30928) Use temurin JRE in test hadoop docker image

Gabor Somogyi created FLINK-30928: - Summary: Use temurin JRE in test hadoop docker image Key: FLINK-30928 URL: https://issues.apache.org/jira/browse/FLINK-30928 Project: Flink Issue Type

[jira] [Created] (FLINK-30800) Add doc entry how to re-generate java doc

Gabor Somogyi created FLINK-30800: - Summary: Add doc entry how to re-generate java doc Key: FLINK-30800 URL: https://issues.apache.org/jira/browse/FLINK-30800 Project: Flink Issue Type: New

Re: [VOTE] Release 1.16.1, release candidate #1

+1 (non-binding) * Verified versions in the poms * Built from source * Verified checksums and signatures * Started basic workloads with kubernetes operator * Verified NOTICE and LICENSE files G On Thu, Jan 26, 2023 at 2:28 PM Dawid Wysakowicz wrote: > +1 (binding) > >- verified checksums

[jira] [Created] (FLINK-30781) Add completed checkpoint check to cluster health check

Gabor Somogyi created FLINK-30781: - Summary: Add completed checkpoint check to cluster health check Key: FLINK-30781 URL: https://issues.apache.org/jira/browse/FLINK-30781 Project: Flink

[jira] [Created] (FLINK-30764) Include generic delegation token params in the main config page

Gabor Somogyi created FLINK-30764: - Summary: Include generic delegation token params in the main config page Key: FLINK-30764 URL: https://issues.apache.org/jira/browse/FLINK-30764 Project: Flink

[jira] [Created] (FLINK-30757) Ugrade busybox version to a pinned version for operator

Gabor Somogyi created FLINK-30757: - Summary: Ugrade busybox version to a pinned version for operator Key: FLINK-30757 URL: https://issues.apache.org/jira/browse/FLINK-30757 Project: Flink

[jira] [Created] (FLINK-30754) Fix ExceptionThrowingDelegationTokenProvider/Receiver multi-threaded test issues

Gabor Somogyi created FLINK-30754: - Summary: Fix ExceptionThrowingDelegationTokenProvider/Receiver multi-threaded test issues Key: FLINK-30754 URL: https://issues.apache.org/jira/browse/FLINK-30754

[jira] [Created] (FLINK-30749) Delegation token provider enabled flag documentation is wrong

Gabor Somogyi created FLINK-30749: - Summary: Delegation token provider enabled flag documentation is wrong Key: FLINK-30749 URL: https://issues.apache.org/jira/browse/FLINK-30749 Project: Flink

[jira] [Created] (FLINK-30713) Add Hadoop related k8s decorators exclude possibility

Gabor Somogyi created FLINK-30713: - Summary: Add Hadoop related k8s decorators exclude possibility Key: FLINK-30713 URL: https://issues.apache.org/jira/browse/FLINK-30713 Project: Flink

[jira] [Created] (FLINK-30704) Add S3 delegation token support

Gabor Somogyi created FLINK-30704: - Summary: Add S3 delegation token support Key: FLINK-30704 URL: https://issues.apache.org/jira/browse/FLINK-30704 Project: Flink Issue Type: New Feature

Re: [NOTICE] Parallel compilation should no longer lock up

Hi Chesnay, Thanks for the efforts! During development I've seen some of the tests are not multi-threaded compliant. Intended to fix what I'm aware of... G On Mon, Jan 16, 2023 at 2:19 PM Chesnay Schepler wrote: > Hello, > > with FLINK-30083 being merged it should now be possible to safely bu

Re: [DISCUSS] Enabling dynamic partition discovery by default in Kafka source

+1 on the overall direction, it's an important feature. I've had a look on the latest master and looks like removed partition handling is not yet added but I think this is essential. https://github.com/apache/flink/blob/28c3e1a3923ba560b559a216985c1abeb794ebaa/flink-connectors/flink-connector-kaf

[jira] [Created] (FLINK-30594) Update Java version because of JDK bug in the operator

Gabor Somogyi created FLINK-30594: - Summary: Update Java version because of JDK bug in the operator Key: FLINK-30594 URL: https://issues.apache.org/jira/browse/FLINK-30594 Project: Flink

[jira] [Created] (FLINK-30429) Flink command stops with IllegalArgumentException

Gabor Somogyi created FLINK-30429: - Summary: Flink command stops with IllegalArgumentException Key: FLINK-30429 URL: https://issues.apache.org/jira/browse/FLINK-30429 Project: Flink Issue

[jira] [Created] (FLINK-30425) Generalize token receive side

Gabor Somogyi created FLINK-30425: - Summary: Generalize token receive side Key: FLINK-30425 URL: https://issues.apache.org/jira/browse/FLINK-30425 Project: Flink Issue Type: Sub-task

  1   2   3   >