Hi Timo,
Thank you for the suggestion. Previously, I thought most parameters were
optional, so the default value was set to true.
Your concern is reasonable. We should declare it as false by default and
developers should explicitly state if a parameter is optional instead of
using our default val
Thanks for the last minute change.
+1 (binding)
Cheers,
Timo
On 05.01.24 08:59, Feng Jin wrote:
Hi Timo,
Thank you for the suggestion. Previously, I thought most parameters were
optional, so the default value was set to true.
Your concern is reasonable. We should declare it as false by defa
Hi Lu,
I believe this feature is very useful. However, I currently lack the
capacity to work on it in the near future. I think it would be great
if you could take on the task. I am willing to offer assistance if
there are any questions about the FLIP, or to review the PR if needed.
Please let me
yong yang created FLINK-34001:
-
Summary: doc diff from code
Key: FLINK-34001
URL: https://issues.apache.org/jira/browse/FLINK-34001
Project: Flink
Issue Type: Bug
Components: API / Stat
Thanks, Paul.
Ferenc and I have been looking into unblocking the Kubernetes path via an
updated implementation for FLINK-28915 to ship the jars conveniently there.
You can expect an updated PR there next week. Looking forward to your
findings in the YARN POC.
On Mon, Dec 11, 2023 at 4:01 AM Paul
Sounds good to me! Thanks
On Fri, Jan 5, 2024 at 12:57 AM Sergey Nuyanzin wrote:
>
> Hi Martijn
> thanks for reminding
> yep, I think you are right we need a release for that.
>
> IIRC so far there is no volunteers for that, so I would volunteer
>
> On Thu, Dec 28, 2023 at 1:27 PM Martijn Visser
Hi Ferenc,
I honestly don't know what happened, but I'm currently pushing the
last changes in. Thanks for the reminder!
Best regards,
Martijn
On Thu, Nov 2, 2023 at 4:49 PM Ferenc Csaky wrote:
>
> Hi Martijn!
>
> Is this work in progress?
>
> Thanks,
> Ferenc
>
>
>
>
> --- Original Message
Hello,
Is there a reason why a type of data skew score (probably just a percentage) is
not shown on the Flink Dashboard / UI?
Currently users have to click on each operator and check how much data each
subtask is processing to tell if there is skew. This is not efficient,
especially cumbersome
Hi everyone,
Please review and vote on the release candidate #1 for the version
3.1.2, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This version is compatible with Flink 1.16.x, 1.17.x and 1.18.x.
The complete staging area is availa
Thanks for driving this
the thing which makes me thinking about -1 (not sure yet and that's why
asking here) is that there is FLINK-33365 [1]
mentioned as a blocker for JDBC connector release at [2]
Since the reason for that is FLINK-16024 [3] as also was explained in
comments for [1].
So should
Hi!
I would like to propose by default to enable unaligned checkpoints and also
simultaneously increase the aligned checkpoints timeout from 0ms to 5s. I
think this change is the right one to do for the majority of Flink users.
For more rationale please take a look into the short FLIP-413 [1].
W
Ops, fixing the topic.
Hi!
>
> I would like to propose by default to enable unaligned checkpoints and
> also simultaneously increase the aligned checkpoints timeout from 0ms to
> 5s. I think this change is the right one to do for the majority of Flink
> users.
>
> For more rationale please take a
Hi,
Hmmm, it would have been good to mark the Jira ticket as a Blocker
then for the JDBC connector. Since it's marked as Critical, it doesn't
appear. It has also been open for multiple months, so it doesn't
really feel like a Blocker. I'm +0 with including this fix, but then
we should either get t
Martijn Visser created FLINK-34002:
--
Summary: Bump CI flink version on flink-connector-elasticsearch
Key: FLINK-34002
URL: https://issues.apache.org/jira/browse/FLINK-34002
Project: Flink
Is
Martijn Visser created FLINK-34003:
--
Summary: Bump CI flink version on flink-connector-hbase
Key: FLINK-34003
URL: https://issues.apache.org/jira/browse/FLINK-34003
Project: Flink
Issue Type
Hi everyone,
Please review and vote on the release candidate #1 for the version
3.0.1, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This version is compatible with Flink 1.16.x, 1.17.x and 1.18.x
The complete staging area is availab
Chesnay Schepler created FLINK-34004:
Summary: TestingCheckpointIDCounter can easily lead to NPEs
Key: FLINK-34004
URL: https://issues.apache.org/jira/browse/FLINK-34004
Project: Flink
Is
Thanks for starting the vote!
Do you mind adding a link from the FLIP to this thread?
Thanks,
Alexey
On Thu, Jan 4, 2024 at 6:48 PM Feng Jin wrote:
> Hi everyone
>
> Thanks for all the feedback about the FLIP-387: Support named parameters
> for functions and call procedures [1] [2] .
>
> I'd li
Thank you Dong and Xuannan!
Yes. We can take on this task. Any help during bootstrapping would be
greatly appreciated! I realize there is already a voting thread "[VOTE]
FLIP-329: Add operator attribute to specify support for object-reuse". What
else do we need?
Best
Lu
On Fri, Jan 5, 2024 at 12
Hi Fang Yong,
Thanks for the response, and I understand the desire to limit the impact of
this FLIP.
I guess I should spend the time to start a new FLIP on switching to Fury, which
could include cleaning up method names.
In the context of “facilitate user understanding”, one aspect of this cle
Bonnie Varghese created FLINK-34005:
---
Summary: Implement restore tests for MiniBatchAssigner node
Key: FLINK-34005
URL: https://issues.apache.org/jira/browse/FLINK-34005
Project: Flink
Issu
Sophia created FLINK-34006:
--
Summary: Flink terminates the execution of an application when
there is a network problem between TaskManagers
Key: FLINK-34006
URL: https://issues.apache.org/jira/browse/FLINK-34006
Zhenqiu Huang created FLINK-34007:
-
Summary: Flink Job stuck in suspend state after recovery from
failure in HA Mode
Key: FLINK-34007
URL: https://issues.apache.org/jira/browse/FLINK-34007
Project: Fl
23 matches
Mail list logo
