Hi Piotrek
> Do you mean to ignore it while processing records, but keep using
> `maxBuffersPerChannel` when calculating the availability of the output?
I think yes, and please Anton Kalashnikov to help double check.
> +1 for just having this as a separate configuration. Is it a big problem
> th
teeguo created FLINK-27478:
--
Summary: failed job by uncertain cause
Key: FLINK-27478
URL: https://issues.apache.org/jira/browse/FLINK-27478
Project: Flink
Issue Type: Bug
Components: API
Hi ChangZhuo,
Yes, it is indeed the tag for 1.15.0,
we have finished affairs like uploading
artifacts, uploading images and creating
tags.
Best,
Yun Gao
--
From:ChangZhuo Chen (陳昌倬)
Send Time:2022 May 3 (Tue.) 10:34
To:dev ; Yun
On Tue, May 03, 2022 at 10:23:33AM +0800, Yun Gao wrote:
> Hi Thomas,
>
> Sorry for the long delay, currently we are very nearly done
> for finalizing the release and we should be able to finish all
> works and announce the release on Thursday.
>
> Best,
> Yun Gao
>
>
>
>
> -
Hi Thomas,
Sorry for the long delay, currently we are very nearly done
for finalizing the release and we should be able to finish all
works and announce the release on Thursday.
Best,
Yun Gao
--
From:Thomas Weise
Send Time:2022
Hi,
Thank you for working on the 1.15.0 release. Is there an update wrt
finalizing the release?
Thanks,
Thomas
On Mon, Apr 25, 2022 at 9:17 PM Yun Gao
wrote:
> I'm happy to announce that we have unanimously approved this release.
>
> There are 6 explicit approving votes, 3 of which are bindin
Hi,
+1 for the general proposal from my side. It would be a nice workaround
flatMaps, WindowOperators and large records issues with unaligned
checkpoints.
> The first task is about ignoring max buffers per channel. This means if
> we request a memory segment from LocalBufferPool and the
> maxBuff
Chesnay Schepler created FLINK-27477:
Summary: Drop flink-yarn test-jar
Key: FLINK-27477
URL: https://issues.apache.org/jira/browse/FLINK-27477
Project: Flink
Issue Type: Technical Debt
Jing Ge created FLINK-27476:
---
Summary: Build new import option that only focus on maven main
classes
Key: FLINK-27476
URL: https://issues.apache.org/jira/browse/FLINK-27476
Project: Flink
Issue T
Martijn Visser created FLINK-27475:
--
Summary: Clean-up unused Maven settings from
flink-connector-elasticsearch
Key: FLINK-27475
URL: https://issues.apache.org/jira/browse/FLINK-27475
Project: Flink
Martijn Visser created FLINK-27474:
--
Summary: Use Hugo build information to derive current branch for
externally hosted documentation
Key: FLINK-27474
URL: https://issues.apache.org/jira/browse/FLINK-27474
Jun Qin created FLINK-27473:
---
Summary: Capture time that a job spends on initializing tasks
Key: FLINK-27473
URL: https://issues.apache.org/jira/browse/FLINK-27473
Project: Flink
Issue Type: Improv
MartijnVisser merged PR #1:
URL: https://github.com/apache/flink-connector-redis/pull/1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@
Martijn Visser created FLINK-27472:
--
Summary: Setup flink-connector-redis repository
Key: FLINK-27472
URL: https://issues.apache.org/jira/browse/FLINK-27472
Project: Flink
Issue Type: New Fe
Sergey Nuyanzin created FLINK-27471:
---
Summary: Add ARRAY_DISTINCT supported in SQL & Table API
Key: FLINK-27471
URL: https://issues.apache.org/jira/browse/FLINK-27471
Project: Flink
Issue T
Chesnay Schepler created FLINK-27470:
Summary: [JUnit5 Migration] Module:
flink-statebackend-heap-spillable
Key: FLINK-27470
URL: https://issues.apache.org/jira/browse/FLINK-27470
Project: Flink
Chesnay Schepler created FLINK-27469:
Summary: Remove CliFrontendRunWithYarnTest
Key: FLINK-27469
URL: https://issues.apache.org/jira/browse/FLINK-27469
Project: Flink
Issue Type: Technic
Matyas Orhidi created FLINK-27468:
-
Summary: Observing JobManager deployment. Previous status: MISSING
Key: FLINK-27468
URL: https://issues.apache.org/jira/browse/FLINK-27468
Project: Flink
I
Chesnay Schepler created FLINK-27467:
Summary: Remove CliFrontendTestBase
Key: FLINK-27467
URL: https://issues.apache.org/jira/browse/FLINK-27467
Project: Flink
Issue Type: Technical Debt
Thanks for the proposal, Lijie.
This is an interesting feature and discussion, and somewhat related to the
design principle about how people should operate Flink.
I think there are three things involved in this FLIP.
a) Detect and report the unstable node.
b) Collect the information of
Thanks for good initiative, Lijie and Zhu!
If it's possible I'd like to participate in development.
I agree with 3rd point of Konstantin's reply - we should consider to move
somehow the information of blocklisted nodes/TMs from active
ResourceManager to non-active ones. Probably storing inside
Zo
I do share the concern between blurring the lines a bit.
That said, I'd prefer to not have any auto-detection and only have an
opt-in mechanism
to manually block processes/nodes. To me this sounds yet again like one
of those
magical mechanisms that will rarely work just right.
An external syst
22 matches
Mail list logo