Hi Bo,
In current Blink implementation, the failover strategy can only confirm restart
the upstream task region for some special exceptions reporeted by downstream
task failure. As you said, if the partition is consumed once by downstream
task, then it would be removed and can not be consumed
Thanks everybody for your feedback and comments.
I will now request the creation of the mailing list, and raise a PR for
updating the Flink website with the info.
On Mon, Jan 28, 2019 at 8:43 AM Becket Qin wrote:
> +1. Great idea!
>
> On Mon, Jan 28, 2019 at 12:02 AM Shaoxuan Wang
> wrote:
>
Hi all,
I ever launched the discussion of "Proposal of external shuffle service" before
and received very helpful feedbacks, especially with @Andrey Zagrebin's
in-depth communication offline.
Based on @Till Rohrmann's suggestion, I launch this separate thread again to
summarize the current
(1) I agree with Aljoscha's line of arguing here. A staleness bot is
quite the opposite of “sweeping things under the rug". A clear and
automated message about the state of a PR provides good value to
contributors, reviewers, and other people monitoring PRs. Asking
committers to proactively close
I played around with the bot and it works pretty well. :-) @Robert:
Are there any plans to contribute the code for the bot to Apache
(potentially in another repository)?
I like Fabians suggestions. Regarding the questions:
1) I would make that dependent on whether you expected the review
Thanks for the clarification. I agree that it only makes sense to
check the points in order. +1 to add this if we can think of a nice
way to do it. I'm not sure how we would enforce the order with the bot
since there is only indirect feedback to a bot command. The only thing
I can think of at the
Alex created FLINK-11438:
Summary: Config for submitted job path
Key: FLINK-11438
URL: https://issues.apache.org/jira/browse/FLINK-11438
Project: Flink
Issue Type: Improvement
Reporter:
Hi Jark,
Thank you for starting this discussion!
I'm very happy about the various efforts to support the Chinese Flink
community.
Offering a translated website and documentation gives Flink a lot more
reach and will help many users.
I think integrating the website and documentation as
Hi Qi,
Thanks for the concerns of this proposal. In Blink we implemented the
YarnShuffleService which is mainly used for batch jobs in production and some
benchmark before. This YarnShuffleService is not within the current proposed
ShuffleManager interface and there is also no ShuffleMaster
Timo Walther created FLINK-11439:
Summary: INSERT INTO flink_sql SELECT * FROM blink_sql
Key: FLINK-11439
URL: https://issues.apache.org/jira/browse/FLINK-11439
Project: Flink
Issue Type:
Hi Robert,
Thanks for working on the bot!
I have a few suggestions / questions:
Suggestions:
1) It would be great to approve multiple boxes in one comment. Either as
> @flinkbot approve contribution consensus
or by
> @flinkbot approve contribution
> @flinkbot approve consensus
2) Extend the
The points in the review template are in the order in which they should be
checked, i.e., first checking the description, then consensus and finally
checking the code.
Currently, it is possible to tick off the code box before checking the
description.
One motivation for the process was to do the
Hi Zhijiang,
I see there’s a YarnShuffleService in newly released Blink branch. Is there any
relationship between that YarnShuffleService and your external shuffle service?
Regards,
Qi
> On Jan 28, 2019, at 8:07 PM, zhijiang
> wrote:
>
> Hi till,
>
> Very glad to receive your feedbacks
Hi Jark
It would be a great idea to contribute the Flink Chinese community website,
which is quite popular among Chinese developers, back to Apache Flink. I think
it could attract more Chinese users and developers.
Alluxio, a distributed storage system, also maintain an official Chinese
I'm late to this party but big +1. Great idea! I think this will help
to better represent the actual Flink community size and increase
interaction between the English and non-English speaking community.
:-)
On Mon, Jan 28, 2019 at 6:02 PM jincheng sun wrote:
>
> +1，I like the idea very much！
>
>
+1，I like the idea very much！
Robert Metzger 于2019年1月24日 周四19:15写道：
> Hey all,
>
> I would like to create a new user support mailing list called "
> user...@flink.apache.org" to cater the Chinese-speaking Flink community.
>
> Why?
> In the last year 24% of the traffic on flink.apache.org came
vinoyang created FLINK-11440:
Summary: AbstractOperatorRestoreTestBase#testMigrationAndRestore
caused IllegalStateException
Key: FLINK-11440
URL: https://issues.apache.org/jira/browse/FLINK-11440
+1，sounds good
Ufuk Celebi 于2019年1月29日周二 上午1:46写道：
> I'm late to this party but big +1. Great idea! I think this will help
> to better represent the actual Flink community size and increase
> interaction between the English and non-English speaking community.
> :-)
>
> On Mon, Jan 28, 2019 at
Hi Jark,
Thank you for starting this discussion!
I think it's great to have an official Chinese doc website, there are so
many Chinese developers can benefit from it. Also, we should think
carefully for the long term maintain the Chinese docs, how to make sure the
docs are the latest and
Thanks Jark starting this discussion!
Hi Fabian, very glad to hear that you like this proposal.
As far as I know， `zh` is the language, `cn` is the territory, such as:
`zh-cn` representative
Simplified Chinese (China) , `zh-tw` representative Traditional Chinese
(Taiwan), So i like the naming
That's good. I want to be involved.
best
qianjin
Yun Tang 于2019年1月29日周二 上午1:00写道：
> Hi Jark
>
> It would be a great idea to contribute the Flink Chinese community
> website, which is quite popular among Chinese developers, back to Apache
> Flink. I think it could attract more Chinese users and
zhijiang created FLINK-11441:
Summary: Remove the schedule mode property from RPDD to TDD
Key: FLINK-11441
URL: https://issues.apache.org/jira/browse/FLINK-11441
Project: Flink
Issue Type:
Hi Jark,
Thank you for starting this discussion.I am very willing to participate in
flink document translation.
Best,
Nicholas
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
Hi Jark,
Thanks a lot for starting the discussion! It would be great to have an official
Flink Chinese doc. For the long term maintaining problem, I think creating a
JIRA when the English documentation is updated is a good idea. Should we add
one item such as "Does this pull request updated
Hi all,
In the past year, the Chinese community is working on building a Chinese
translated Flink website (http://flink.apache.org) and documents (
http://ci.apache.org/projects/flink/flink-docs-master/) in order to help
Chinese speaking users. This is http://flink-china.org and it has received
a
Hi till,
Very glad to receive your feedbacks and it is atually very helpful.
The proposed ShuffleMaster in JM would be involved in many existing processes,
such as task deployment, task failover, TM release, so it might be interactive
with corresponding Scheduler, FailoverStrategy, SlotPool
Hi Stephan & Piotrek,
Thank you for feedback.
It seems that there are a lot of things to do in community. I am just
afraid that this discussion may be forgotten since there so many proposals
recently.
Anyway, wish to see the split topics soon :)
Piotr Nowojski 于2019年1月24日周四 下午8:21写道：
> Hi
Thank Bo for your interesting example, and it seems the current task retry
strategy could be more efficient. The ExternalShuffleService refactor is an
exciting improvement for both shuffle and failover. And Bo proposed to make
the SubPartition buffers available for possible later retry until the
Thanks for creating the FLIP-31 for the external shuffle service Zhijiang.
It looks good to me.
One thing which is not fully clear to me yet is how the lifecycle
management of the partitions integrates with the slot management. At the
moment, conceptually we consider the partition data being
Hi Lakshmi，
As Nagajun mentioned, you might want to configure quota on the Kafka broker
side for your Flink connector client.
Thanks,
Jiangjie (Becket) Qin
On Sat, Jan 26, 2019 at 10:44 AM Ning Shi wrote:
> > We have a Flink job reading from Kafka (specifically it uses
> >
vinoyang created FLINK-11437:
Summary:
EventTimeWindowCheckpointingITCase#testTumblingTimeWindowWithKVStateMaxMaxParallelism
caused CancellationException
Key: FLINK-11437
URL:
Hi,
We were trying to collect the sideOutput.
But failed to understand as to how to convert this windowed stream to a
datastream.
final OutputTag>
lateOutputTag = new OutputTag>("late-data"){};
withTime.keyBy(0, 2)
.window(TumblingEventTimeWindows.of(Time.minutes(5)))
32 matches
Mail list logo
