Hi,
Thanks for driving this, I think it is really helpful for jobs suffering
from backpressure.
Best,
Yingjie
Anton,Kalashnikov 于2021年7月9日周五 下午10:59写道：
> Hey!
>
> There is a wish to decrease amount of in-flight data which can improve
> aligned checkpoint time(fewer in-flight data to process
Caizhi Weng created FLINK-23374:
---
Summary: Clean up logs produced by code splitter
Key: FLINK-23374
URL: https://issues.apache.org/jira/browse/FLINK-23374
Project: Flink
Issue Type: Sub-task
Hi Becket,
I believe 1+2 has been answered by Chesnay already. Just to add to 2: I'm
not the biggest fan of reusing task metrics but that's what FLIP-33 and
different folks suggested. I'd probably keep task I/O metrics only for
internal things and add a new metric for external calls. Then, we
@Eron Wright The per-split watermarks are the
default in the new source interface (FLIP-27) and come for free if you use
the SplitReader.
Based on that, it is also possible to unsubscribe individual splits to
solve the alignment in the case where operators have multiple splits
assigned.
Piotr
Hi Stephan,
Thank you so much for all these practical suggestions.
I agree that hybrid batch/streaming execution is an awesome idea and that
no checkpoint could be successful during the batch phase. However, the
checkpoint could fail frequently because of the large batch size, which
might be
Hello everyone,
I just merged the last PR for FLINK-14105, with which flink-runtime is
now officially scala-free. *fireworks*
What does that mean in practice?
a) flink-runtime no longer has a scala-suffix, which cascaded into other
modules (e.g., our reporter modules). This _may_
Hi all!
I would like to propose that we make it a project standard that when
upgrading a dependency, deprecation issues arising from that need to be
fixed in the same step. If the new dependency version deprecates a method
in favor of another method, all usages in the code need to be replaced
Timo Walther created FLINK-23373:
Summary: Support object reuse disabled in OperatorChain
Key: FLINK-23373
URL: https://issues.apache.org/jira/browse/FLINK-23373
Project: Flink
Issue Type:
Timo Walther created FLINK-23372:
Summary: Disable AllVerticesInSameSlotSharingGroupByDefault in
DataStream batch mode
Key: FLINK-23372
URL: https://issues.apache.org/jira/browse/FLINK-23372
Project:
Hi Godfrey,
Are you continuing with the 1.11.4 release process?
Cheers,
Till
On Tue, Jul 6, 2021 at 1:15 PM Chesnay Schepler wrote:
> Since 1.11.4 is about releasing the commits we already have merged
> between 1.11.3 and 1.13.0, I would suggest to not add additional fixes.
>
> On 06/07/2021
Hi everyone,
FLINK-23233 has been merged. We can continue with the release process.
Cheers,
Till
On Wed, Jul 7, 2021 at 2:00 PM Yun Tang wrote:
> Since FLINK-23233 brings concerns to many guys, and this release candidate
> #1 had not received enough binding +1 from PMCs, I think we could
Hi everyone,
FLINK-23233 has been merged. We can continue with the release process.
Cheers,
Till
On Wed, Jul 7, 2021 at 1:29 PM Jingsong Li wrote:
> Hi all,
>
> Thanks Xiongtong, Leonard, Yang, JING for the voting. Thanks Till for the
> information.
>
> +1 for canceling this RC. That should
Timo Walther created FLINK-23371:
Summary: Disable AutoWatermarkInterval for bounded legacy sources
Key: FLINK-23371
URL: https://issues.apache.org/jira/browse/FLINK-23371
Project: Flink
Timo Walther created FLINK-23370:
Summary: Propagate Boundedness of SourceFunctionProvider to
Transformation
Key: FLINK-23370
URL: https://issues.apache.org/jira/browse/FLINK-23370
Project: Flink
Before jumping into the designs of other mechanisms, can we clarify whether
adjusting checkpointing is really the right approach here?
What about storing empty state in the checkpoints, so that any recovery
simply does a full replay of the input.
Regarding the hybrid batch/streaming execution:
Re 1: We don't expose the reuse* methods, because the proposed
OperatorIOMetricGroup is a separate interface from the existing
implementations (which will be renamed and implement the new interface).
Re 2: Currently the plan is to re-use the "new" numByesIn/Out counters
for tasks ("new"
Ingo Bürk created FLINK-23369:
-
Summary: Use enums for connector options
Key: FLINK-23369
URL: https://issues.apache.org/jira/browse/FLINK-23369
Project: Flink
Issue Type: Sub-task
Hi Arvid,
Thanks for the proposal. I like the idea of exposing concrete metric group
class so that users can access the predefined metrics.
A few questions are following:
1. When exposing the OperatorIOMetrics to the users, we are also exposing
the reuseInputMetricsForTask to the users. Should
Thanks to all of you.
Best,
Yang
XING JIN 于2021年7月8日周四 上午11:46写道：
> Congratulations Yang Wang!
>
> Austin Cawley-Edwards 于2021年7月7日周三 下午9:29写道：
>
> > Congrats Yang!
> >
> > On Wed, Jul 7, 2021 at 7:26 AM Jingsong Li
> wrote:
> >
> > > Congratulations, Yang!
> > >
> > > Best,
> > > Jingsong
>
Hi devs and users,
This topic was originally discussed and reached a consensus in [1]. Because
the change touches the pluggable shuffle interface, though not annotated as
public currently, some users may be using it already. To avoid bring
compatibility issues to customized shuffle plugins
Huang Xingbo created FLINK-23368:
Summary: Fix the wrong mapping of state cache in PyFlink
Key: FLINK-23368
URL: https://issues.apache.org/jira/browse/FLINK-23368
Project: Flink
Issue Type:
21 matches
Mail list logo
