Regarding setting the feature freeze date to late September, I have some
concern that it might make
the development time of 1.12 too short.
One reason for this is we took too much time (about 1.5 month, from mid of
May to beginning of July)
for testing 1.11. It's not ideal but further squeeze the
ming li created FLINK-18808:
---
Summary: Task-level numRecordsOut metric may be underestimated
Key: FLINK-18808
URL: https://issues.apache.org/jira/browse/FLINK-18808
Project: Flink
Issue Type:
Hi all,
I would like to start the vote for FLIP-132 [1], which has been discussed and
reached a consensus in the discussion thread [2].
The vote will be open until 7th August (72h), unless there is an objection or
not enough votes.
Best,
Leonard
[1]
Thanks Konstantin,
Regarding your questions, hope my comments has address your questions and I
also add a few explanation in the FLIP.
Thank you all for the feedback,
It seems everyone involved in this thread has reached a consensus.
I will start a vote thread later.
Best,
Leonard
> 在
Dian Fu created FLINK-18807:
---
Summary: FlinkKafkaProducerITCase.testScaleUpAfterScalingDown
failed with "Timeout expired after 6milliseconds while awaiting
EndTxn(COMMIT)"
Key: FLINK-18807
URL:
| |
朱雄山
|
|
zhuxiongs...@163.com
|
签名由网易邮箱大师定制
+ link
https://www.flink-forward.org/global-2020/speakers
On Mon, Aug 3, 2020 at 11:25 AM Seth Wiesman wrote:
> Hi everyone!
>
> I'm very excited to announce that the speaker lineup for Flink Forward
> Global has been released. This is a fully online conference on October
> 21-22 and tickets
Hi everyone!
I'm very excited to announce that the speaker lineup for Flink Forward
Global has been released. This is a fully online conference on October
21-22 and tickets are free. The lineup includes 45+ speakers from the
companies like of Spotify, AWS, Netflix, Houzz, Workday hear their Flink
Jincheng,
One thing that I like about the way that the documentation is currently
organized is that it's relatively straightforward to compare the Python API
with the Java and Scala versions. I'm concerned that if the PyFlink docs
are more independent, it will be challenging to respond to
-1
I'm sorry to be late to the discussion but I have some concerns I've
brought up in the discussion thread.
Seth
On Mon, Aug 3, 2020 at 3:00 AM jincheng sun
wrote:
> Hi everyone,
>
> I would like to start the vote for FLIP-133[1], which is discussed and
> reached a consensus through the
Hi Jincheng,
I'm very excited to see the enthusiasm for documentation work but I am
concerned about the communities long term ability to maintain this
contribution. In particular, I'm concerned that this proposal duplicates a
lot of content that will quickly get out of sync. So far the community
Nico Kruber created FLINK-18806:
---
Summary: Taskmanager doesn't start up with error in config
Key: FLINK-18806
URL: https://issues.apache.org/jira/browse/FLINK-18806
Project: Flink
Issue Type:
Thanks Lennard for driving this FLIP.
Looks good to me.
Best,
Godfrey
Jark Wu 于2020年8月3日周一 下午12:04写道：
> Thanks Leonard for the great FLIP. I think it is in very good shape.
> +1 to start a vote.
>
> Best,
> Jark
>
> On Fri, 31 Jul 2020 at 17:56, Fabian Hueske wrote:
>
> > Hi Leonard,
> >
> >
Chesnay Schepler created FLINK-18805:
Summary: ConfigDocsGenerator does not handle multiple upper
characters properly
Key: FLINK-18805
URL: https://issues.apache.org/jira/browse/FLINK-18805
Chesnay Schepler created FLINK-18804:
Summary: ConfigDocsGenerator should not create files if they
contain no options
Key: FLINK-18804
URL: https://issues.apache.org/jira/browse/FLINK-18804
Libin Qin created FLINK-18803:
-
Summary: JobGraph cannot be GC when submit via
RemoteStreamEnvironment in attach mode
Key: FLINK-18803
URL: https://issues.apache.org/jira/browse/FLINK-18803
Project:
Qingsheng Ren created FLINK-18802:
-
Summary: Creating an uber jar when packaging flink-avro
Key: FLINK-18802
URL: https://issues.apache.org/jira/browse/FLINK-18802
Project: Flink
Issue Type:
Hi everyone,
I would like to start the vote for FLIP-36[1], which is discussed and reached a
consensus through the discussion thread[2].
The vote will be open until 6th August(72h), unless there is an objection or
not enough votes.
Best,
Xuannan
[1]:
Thanks for the pointer!
On 03.08.20 10:29, Till Rohrmann wrote:
Hi Xia Rui,
thanks for reporting this issue. I think FLINK-15116 [1] caused the
regression. The problem is indeed that we no longer set the
lastJobExecutionResult when using the ContextEnvironment. The problem has
not surfaced
Wei Zhong created FLINK-18801:
-
Summary: Add the new document "10 minutes to PyFlink"
Key: FLINK-18801
URL: https://issues.apache.org/jira/browse/FLINK-18801
Project: Flink
Issue Type: Sub-task
Hi Xia Rui,
thanks for reporting this issue. I think FLINK-15116 [1] caused the
regression. The problem is indeed that we no longer set the
lastJobExecutionResult when using the ContextEnvironment. The problem has
not surfaced since with other ExecutionEnvironments, we still set the field
Hi everyone,
I would like to start the vote for FLIP-133[1], which is discussed and
reached a consensus through the discussion thread[2].
The vote will be open until 6th August (72h), unless there is an objection
or not enough votes.
Best,
Jincheng
[1]:
Hi Paul,
looking briefly at the code, it should be possible to execute the snapshot
procedure for every Bucket in snapshotActiveBuckets in parallel and to wait
for the result in the very same method. I've also pulled in Klou who
implemented this feature and who might give a more profound
Would be great if you could join the contribution of PyFlink
documentation @Marta !
Thanks for all of the positive feedback. I will start a formal vote then
later...
Best,
Jincheng
Shuiqiang Chen 于2020年8月3日周一 上午9:56写道：
> Hi jincheng,
>
> Thanks for the discussion. +1 for the FLIP.
>
> A
24 matches
Mail list logo
