Hi,
We have to keep in mind that if a users asks for a new Jira account, that
person will need to provide its email address which is the Flink PMC
processing personal identifiable information. There needs to be a careful
process for that and to be honest, I don't think the ASF should do this
from
Hi guys:
I'd like to initiate a discussion about adding command-line arguments to
support user-dependent jar packages.
Currently flink supports user's main jars through -jarfile or without
setting this , the flink client will treat the first argument after that as
the user master jar package
Hi guys:
I'd like to initiate a discussion about adding command-line arguments to
support user-dependent jar packages.
Currently flink supports user's main jars through -jarfile or without
setting this , the flink client will treat the first argument after that as
the user master jar package
Hi guys:
I'd like to initiate a discussion about adding command-line arguments to
support user-dependent jar packages.
Currently flink supports user's main jars through -jarfile or without
setting this , the flink client will treat the first argument after that as
the user master jar package
Thanks, Yanfei for driving this to monitor the performance in the Apache Flink
Slack Channel.
Look forward to the workflow and detailed descriptions of flink-dev-benchmarks.
Best
Yun Tang
From: Hangxiang Yu
Sent: Thursday, October 27, 2022 10:59
To:
Jingsong Lee created FLINK-29774:
Summary: Introduce options metadata table
Key: FLINK-29774
URL: https://issues.apache.org/jira/browse/FLINK-29774
Project: Flink
Issue Type: Sub-task
Caizhi Weng created FLINK-29773:
---
Summary: PreAggregationITCase.LastValueAggregation and
PreAggregationITCase.LastNonNullValueAggregation are unstable
Key: FLINK-29773
URL:
Hi, Yanfei.
Thanks for driving this.
It could help us to detect and resolve the regression problem quickly and
officially.
I'd like to join as a maintainer.
Looking forward to the workflow.
On Wed, Oct 26, 2022 at 5:18 PM Yuan Mei wrote:
> Thanks, Yanfei, to drive this and make the performance
shizhengchao created FLINK-29772:
Summary: Kafka table source scan blocked
Key: FLINK-29772
URL: https://issues.apache.org/jira/browse/FLINK-29772
Project: Flink
Issue Type: Bug
Hi Max,
Thanks for reviewing.
For this Flip 264, yes, we will only focus on abstracting RPC calls between
the task and the job manager for communications and won't touch watermark
checkpoint.
If the coordinator doesn't need RPC calls to talk with subtasks, then it
can define context without
Hello,
I agree with Gyula. My preference is also option 1, and as a fallback
option 3. Handling new user account requests will be manageable, especially
via slack. We could setup a dedicated channel for people to ask for
Jira/wiki access.
Thanks,
Danny
On Wed, 26 Oct 2022, 12:16 Gyula Fóra,
Hi Gordon (and others),
I'm also using this project for stateful messaging, including messaging
among functions.
I've contributed a small amount of code in the past and have also enabled
Flink 1.15 compatibility in a local fork, so I might be able to help out
here.
Thanks,
Galen
On Wed, Oct
Hi Gordon,
We’re using it for stateful messaging, and also calling remote Python-based
functions.
So yes, also very interested in what is going to happen with the this
subproject in the future.
— Ken
> Begin forwarded message:
>
> From: "Tzu-Li (Gordon) Tai"
> Subject: Re: Stateful
Hi Filip,
Thanks for bringing this up.
The hard truth is that committers who were previously active on the
StateFun subproject, including myself, all currently have other focuses.
Indeed, we may need to discuss with the community on how to proceed if
there seems to be no continued committer
As far as I know the original authors are not working on this
implementation anymore. Other folks might be able to provide more context.
Instead of rewriting your code to be a native Flink job, would it be an
option for your team to pick up the pull request to port statefun to Flink
1.15?
-Max
Gyula Fora created FLINK-29771:
--
Summary: Fix flaky RollbackTest
Key: FLINK-29771
URL: https://issues.apache.org/jira/browse/FLINK-29771
Project: Flink
Issue Type: Bug
Components:
Thanks for the proposal, Gang! This is indeed somewhat of a bigger change.
The coordinator for sources, as part of FLIP-27, was specifically added to
synchronize the global watermark and to assign splits dynamically. However,
it practically allows arbitrary RPC calls between the task and the job
For those that are interested, I have a draft PR open for this
https://github.com/apache/flink/pull/21128 - Feel free to have a look.
I'm not sure yet why the Flink CI fails, since these tests are passing
locally.
Thanks,
Martijn
On Tue, Oct 25, 2022 at 10:21 AM Matthias Pohl
wrote:
> >
Hi Gabor,
They are absolutely not coupled, I'm merely mentioning it because it could
"waste" potentially someone's time: first by creating a bandaid which would
then need to be replaced with a more permanent solution. Could be fine, but
it all depends on how much effort & errorprone the bandaid
Bo Cui created FLINK-29770:
--
Summary: hbase connector supports out-of-order data
Key: FLINK-29770
URL: https://issues.apache.org/jira/browse/FLINK-29770
Project: Flink
Issue Type: Improvement
Weijie Guo created FLINK-29769:
--
Summary: Further limit the explosion range of failover in hybrid
shuffle mode
Key: FLINK-29769
URL: https://issues.apache.org/jira/browse/FLINK-29769
Project: Flink
+1, thanks Fabian.
Am Mi., 26. Okt. 2022 um 08:26 Uhr schrieb Danny Cranmer <
dannycran...@apache.org>:
> +1, thanks for driving this Fabian.
>
> Danny,
>
> On Wed, Oct 26, 2022 at 2:22 AM yuxia wrote:
>
> > Thanks for driving this.
> > +1 for release 1.15.3
> >
> > Best regards,
> > Yuxia
> >
Weijie Guo created FLINK-29768:
--
Summary: Hybrid shuffle supports the update of ResultPartition
information
Key: FLINK-29768
URL: https://issues.apache.org/jira/browse/FLINK-29768
Project: Flink
Weijie Guo created FLINK-29767:
--
Summary: Adaptive batch scheduler supports hybrid shuffle
Key: FLINK-29767
URL: https://issues.apache.org/jira/browse/FLINK-29767
Project: Flink
Issue Type:
Weijie Guo created FLINK-29766:
--
Summary: Speculative execution supports hybrid shuffle mode.
Key: FLINK-29766
URL: https://issues.apache.org/jira/browse/FLINK-29766
Project: Flink
Issue Type:
Hi!
I would also personally prefer staying with JIRA given the feature set and
the past positive experience with it.
I think the structured nature of JIRA with flexible components, issue
types, epics, release handling etc have been a great benefit to the
project, it would be a shame to give some
Hi, I noticed that the development on stateful functions has come to a bit
of a halt, with a pull request to update statefun to use Flink 1.15 being
in the `open` state since May 2022.
What do we think is the future of this sub-project?
The background to this question is that my team is on a
Hi Martijn,
> I'm not sure that creating another bandaid is a good idea.
I think we have multiple issues here which are not coupled:
* Hadoop config handling in Flink is not consistent (for example runtime
uses hadoop FS connector code and each connector has it's own
implementation)
* S3
Thanks, Yanfei, to drive this and make the performance monitoring publicly
available.
Looking forward to seeing the workflow, and more details as Martijn
mentioned.
Best
Yuan
On Wed, Oct 26, 2022 at 2:59 PM Martijn Visser
wrote:
> Hi Yanfei Lei,
>
> Thanks for setting this up! It would be
Aqib Mehmood created FLINK-29765:
Summary: SQL query not executing properly
Key: FLINK-29765
URL: https://issues.apache.org/jira/browse/FLINK-29765
Project: Flink
Issue Type: Bug
Affects
Hi everyone,
I am pleased to announce that we have unanimously approved this release
candidate:
There are 14 approving votes, 3 of which are binding:
- Xintong （binding)
- Yun Tang (non-binding)
- Lijie (non-binding)
- Xingbo (non-binding)
- Leonard Xu (non-binding)
- Sergey (non-binding)
-
Thank you all for helping to verify the release. Really appreciated!
I will conclude the vote in a separate thread.
Best,
Xingbo
Yang Wang 于2022年10月25日周二 18:44写道：
> +1(binding)
>
> * Built from source
> * Verified signature and checksum
> * Build docker image with flink binary
> * Submit/stop
+1 binding
Thanks Danny!
On Wed, Oct 26, 2022 at 8:48 AM Danny Cranmer
wrote:
> Hello all,
>
> As discussed in the discussion thread [1], I propose to create a dedicated
> repository for AWS connectors called flink-connector-aws. This will house
> 3x connectors: Amazon Kinesis Data Streams,
Hi Yanfei Lei,
Thanks for setting this up! It would be interesting to also know which
aspects of Flink are monitored for "performance". I'm assuming there are
specific pieces of functionality that are performance tested, but it would
be great if this would be written down somewhere (next to a
Hello all,
As discussed in the discussion thread [1], I propose to create a dedicated
repository for AWS connectors called flink-connector-aws. This will house
3x connectors: Amazon Kinesis Data Streams, Amazon Kinesis Data Firehose
and Amazon DynamoDB and any future AWS connectors. We will also
+1, thanks for driving this Fabian.
Danny,
On Wed, Oct 26, 2022 at 2:22 AM yuxia wrote:
> Thanks for driving this.
> +1 for release 1.15.3
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Leonard Xu"
> 收件人: "dev"
> 发送时间: 星期二, 2022年 10 月 25日 下午 10:00:47
> 主题: Re: [DISCUSS] Release Flink
Hi yanfei,
Thanks for driving this! It's a great help.
I would like to join as a maintainer.
Best,
Zakelly
On Wed, Oct 26, 2022 at 11:32 AM yanfei lei wrote:
>
> Hi everyone,
>
> As discussed earlier, we plan to create a benchmark channel in Apache Flink
> slack[1], but the plan was shelved
37 matches
Mail list logo
