Thanks Chesnay!
Scala-free is really nice!
Best,
Jingsong
On Fri, Jul 16, 2021 at 2:01 PM Zhu Zhu wrote:
> Thanks Chesnay for this great work!
>
> Thanks,
> Zhu
>
> Steven Wu 于2021年7月16日周五 上午12:49写道：
>
> > This is awesome. Thank you, Chesney!
> >
> > On Wed, Jul 14, 2021 at 1:50 AM Yun Tang
Thanks Chesnay for this great work!
Thanks,
Zhu
Steven Wu 于2021年7月16日周五 上午12:49写道：
> This is awesome. Thank you, Chesney!
>
> On Wed, Jul 14, 2021 at 1:50 AM Yun Tang wrote:
>
> > Great news, thanks for Chesnay's work!
> >
> > Best
> > Yun Tang
> >
> > From: Ma
Xintong Song created FLINK-23406:
Summary:
ClusterUncaughtExceptionHandlerITCase.testExitDueToUncaughtException fails on
azure
Key: FLINK-23406
URL: https://issues.apache.org/jira/browse/FLINK-23406
Xintong Song created FLINK-23405:
Summary:
FlinkKafkaProducerMigrationOperatorTest.testRestoreProducer fails due to
BindException
Key: FLINK-23405
URL: https://issues.apache.org/jira/browse/FLINK-23405
Hi Till,
> 1) Does endOfInput entail sending of the MAX_WATERMARK?
>
> 2) StreamOperator.finish says to flush all buffered events. Would a
> WindowOperator close all windows and emit the results upon calling
> finish, for example?
1) currently they are independent but parallel mechanisms. With ev
alfred.zou created FLINK-23404:
--
Summary: function UNIX_TIMESTAMP's result incorrect when format is
'EEE MMM dd HH:mm:ss z '
Key: FLINK-23404
URL: https://issues.apache.org/jira/browse/FLINK-23404
Pr
Hi Steven,
The semantics are unchanged compared to FLIP-33 [1] but I see your point.
In reality, pending records would be mostly for event storage systems
(Kafka, Kinesis, ...). Here, we would report the consumer lag effectively.
If consumer lag is more prominent, we could also rename it.
For pe
I really like the new idea.
On Thu, Jul 15, 2021 at 11:51 AM Piotr Nowojski
wrote:
> Hi Till,
>
> > I assume that buffer sizes are only
> > changed for newly assigned buffers/credits, right? Otherwise, the data
> > could already be on the wire and then it wouldn't fit on the receiver
> side.
>
Hi Till,
> I assume that buffer sizes are only
> changed for newly assigned buffers/credits, right? Otherwise, the data
> could already be on the wire and then it wouldn't fit on the receiver
side.
> Or do we have a back channel mechanism to tell the sender that a part of a
> buffer needs to be r
Till Rohrmann created FLINK-23403:
-
Summary: Decrease default values for heartbeat timeout and interval
Key: FLINK-23403
URL: https://issues.apache.org/jira/browse/FLINK-23403
Project: Flink
This is awesome. Thank you, Chesney!
On Wed, Jul 14, 2021 at 1:50 AM Yun Tang wrote:
> Great news, thanks for Chesnay's work!
>
> Best
> Yun Tang
>
> From: Martijn Visser
> Sent: Wednesday, July 14, 2021 16:05
> To: dev@flink.apache.org
> Subject: Re: [NOTICE]
Hi everyone,
Thanks a lot for creating this FLIP Anton and Piotr. I think it looks like
a very promising solution for speeding up our checkpoints and being able to
create them more reliably.
Following up on Steven's question: I assume that buffer sizes are only
changed for newly assigned buffers/
Thanks for updating the FLIP. Based on the new section about
stop-with-savepoint [--drain] I got two other questions:
1) Does endOfInput entail sending of the MAX_WATERMARK?
2) StreamOperator.finish says to flush all buffered events. Would a
WindowOperator close all windows and emit the results u
Timo Walther created FLINK-23402:
Summary: Expose a consistent GlobalDataExchangeMode
Key: FLINK-23402
URL: https://issues.apache.org/jira/browse/FLINK-23402
Project: Flink
Issue Type: Sub-ta
Dian Fu created FLINK-23401:
---
Summary: Separate data and timer connection into different channel
Key: FLINK-23401
URL: https://issues.apache.org/jira/browse/FLINK-23401
Project: Flink
Issue Type: S
Dian Fu created FLINK-23400:
---
Summary: Support to decode a single record for the Python coder
Key: FLINK-23400
URL: https://issues.apache.org/jira/browse/FLINK-23400
Project: Flink
Issue Type: Sub-
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.12.5,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
*
Yanfei Lei created FLINK-23399:
--
Summary: Add a benchmark for rescaling
Key: FLINK-23399
URL: https://issues.apache.org/jira/browse/FLINK-23399
Project: Flink
Issue Type: Improvement
C
Piotr Nowojski created FLINK-23398:
--
Summary: State backend benchmarks are failing
Key: FLINK-23398
URL: https://issues.apache.org/jira/browse/FLINK-23398
Project: Flink
Issue Type: Bug
Dino Zhang created FLINK-23397:
--
Summary: [DOCS] task_failure_recovery page return 404
Key: FLINK-23397
URL: https://issues.apache.org/jira/browse/FLINK-23397
Project: Flink
Issue Type: Bug
Hello,
I recently made a change to confluence and jira to integrate the user
permissions with the apache accounts, such that any PMC member or
committer automatically gain privileges if they become one. As part of
that I also removed all explicit permission settings for these individuals.
It
Maciej Bryński created FLINK-23396:
--
Summary: Exception when restoring SQL job after upgrade from 1.12
to 1.13
Key: FLINK-23396
URL: https://issues.apache.org/jira/browse/FLINK-23396
Project: Flink
>
> If someone started preparing a junit5 migration PR they will run into
> merge conflicts if everyone now starts replacing these instances at will.
This sounds like a good case for fixing it in one step during the upgrade.
Otherwise folks will start individually fixing this individually when th
Chesnay Schepler created FLINK-23395:
Summary: Bump Okhttp to 3.14.9
Key: FLINK-23395
URL: https://issues.apache.org/jira/browse/FLINK-23395
Project: Flink
Issue Type: Bug
Compo
Jingsong Lee created FLINK-23394:
Summary: Add the HbaseOptions to the configuration generator
Key: FLINK-23394
URL: https://issues.apache.org/jira/browse/FLINK-23394
Project: Flink
Issue Typ
Great, thanks a lot Jingsong!
Cheers,
Till
On Thu, Jul 15, 2021 at 5:00 AM Jingsong Li wrote:
> Hi Till and Flinkers working for the FLINK-23233,
>
> Thanks for the effort!
>
> RC2 is on the way.
>
> Best,
> Jingsong
>
> On Tue, Jul 13, 2021 at 8:35 PM Till Rohrmann
> wrote:
>
> > Hi everyone,
Thanks a lot for your answers and clarifications Yun.
1+2) Agreed, this can be a future improvement if this becomes a problem.
3) Great, this will help a lot with understanding the FLIP.
Cheers,
Till
On Wed, Jul 14, 2021 at 5:41 PM Yun Gao
wrote:
> Hi Till,
>
> Very thanks for the review and
BIG +1 for this. Thanks Stephan for starting this discussion.
Too many warnings in IDE and mvn build are frustrating. We can have the
opportunity to avoid the degradation of code quality.
Best,
Jingsong
On Thu, Jul 15, 2021 at 3:26 PM David Morávek
wrote:
> I know that sonar can report back by
I know that sonar can report back by adding a comment to the issue (very
similar way the FlinkBot does) and can block the merge (probably using
check runs api [1]), if some quality gate fails. I was never setting it up,
so I'd need to take a closer look. This is a feature set we were using on
GH in
Chesnay Schepler created FLINK-23393:
Summary: Benchmarks do not support logging
Key: FLINK-23393
URL: https://issues.apache.org/jira/browse/FLINK-23393
Project: Flink
Issue Type: Bug
Hi everyone,
Please review and vote on the release candidate #1 for the version 14.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
31 matches
Mail list logo
