On Tue, Feb 12, 2019 at 3:17 PM Jark Wu wrote:
> Hi Gordon,
>
> I totally agree with your proposal.
>
> A minor comment: "updated required English documentation" should be
> "updated required Chinese documentation" ?
>
Actually, that was what I meant to say.
My intention is that at least the
Hi Gordon,
I totally agree with your proposal.
A minor comment: "updated required English documentation" should be
"updated required Chinese documentation" ?
Btw, I like the "zh-doc" label!
Regards,
Jark
On Tue, 12 Feb 2019 at 14:48, Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> While I 100% agree
Hi,
While I 100% agree with @Xingcan that we should try to avoid adding extra
burden for contributors, at the very least, creating JIRA issues for adding
missing Chinese / English document updates must be done.
In the past, even with English documentation only, we already had the
problem of
Hi @Xingcan,
> I think assigning pages to someones and synchronizing them regularly may
be a better idea.
> 1. We encourage contributors who are familiar with Chinese and would like
to do the translation to provide Chinese doc updates in sync, but should
not add extra burden (even like creating
Hi folks,
Sorry for late response, It seems we reach consensus on this, I will create
FLIP for this with more detailed design
Thomas Weise 于2018年12月21日周五 上午11:43写道：
> Great to see this discussion seeded! The problems you face with the
> Zeppelin integration are also affecting other downstream
Jark Wu created FLINK-11581:
---
Summary: Add Chinese document contribution guideline
Key: FLINK-11581
URL: https://issues.apache.org/jira/browse/FLINK-11581
Project: Flink
Issue Type: Sub-task
Hi all,
Thanks @Jark for creating the translation terminology document! I think the
idea of keeping some of the terminologies untranslated and keeping such
document in place is absolutely good.
I actually share the same concern with @Shaoxuan regarding the discrepancy
getting larger. The dilemma
I created a PR with the implementation described above —
https://github.com/apache/flink/pull/7679. Please provide feedback :)
Thanks
Lakshmi
On Thu, Feb 7, 2019 at 11:04 AM Lakshmi Gururaja Rao wrote:
> Apologies for the delay in responding here.
>
> The idea of making the Ratelimiter
Nico Kruber created FLINK-11579:
---
Summary: Support Netty SslEngine based on openSSL
Key: FLINK-11579
URL: https://issues.apache.org/jira/browse/FLINK-11579
Project: Flink
Issue Type:
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.7.2,
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],
*
Hi all,
I’m currently working in my research on a variant of Flink which allows to
assign subpartitions while runtime to TaskExecutors (just having a look at
joins for the moment). In this variant, I made some changes to the
ResultPartitionDeploymentDescriptor which lead to the creation of many
Hi,
Thank you for working on this.
I think assigning pages to someones and synchronizing them regularly may be a
better idea.
1. We encourage contributors who are familiar with Chinese and would like to do
the translation to provide Chinese doc updates in sync, but should not add
extra
Gary Yao created FLINK-11578:
Summary: Check and port BackPressureStatsTrackerImplITCase to new
code base if necessary
Key: FLINK-11578
URL: https://issues.apache.org/jira/browse/FLINK-11578
Project:
Gary Yao created FLINK-11577:
Summary: Check and port StackTraceSampleCoordinatorITCase to new
code base if necessary
Key: FLINK-11577
URL: https://issues.apache.org/jira/browse/FLINK-11577
Project:
Sure, sounds very good @Robert Metzger , @Hequn Cheng
@Dian Fu I will post the discussion of 1.6.4 later.
Best,
Jincheng
Robert Metzger 于2019年2月11日周一 下午8:46写道：
> Cool! Then let's do the release together. I haven't done it in a while, but
> we'll manage.
>
> Could you start a separate
Hi,
+1 on both 1.7.2 and 1.6.4. By then we can have a more stable release.
Best, Hequn
On Mon, Feb 11, 2019 at 8:46 PM Robert Metzger wrote:
> Cool! Then let's do the release together. I haven't done it in a while, but
> we'll manage.
>
> Could you start a separate [DISCUSS] thread for the
Cool! Then let's do the release together. I haven't done it in a while, but
we'll manage.
Could you start a separate [DISCUSS] thread for the 1.6.4 release?
On Mon, Feb 11, 2019 at 1:39 PM jincheng sun
wrote:
> Thank you for agreeing to release Flink 1.6.4. @Robert Metzger
> @Till Rohrmann
Thank you for agreeing to release Flink 1.6.4. @Robert Metzger
@Till Rohrmann !
I believe that users of Flink will also very much expect the release of
Flink 1.6.4.
I am very willing to contribute to the Flink community in any way. Of
course, it is a great honor to be able to do the release
+1 to release 1.7.2.
Also +1 to the release 1.6.4 as there are already a few critical bug fixes in
the release-1.6 branch. It would be great to start a new thread for the vote of
release 1.6.4 to see if there are any critical bug fixes wanted to merged in
this release.
Regards,
Dian
> 在
+1 on a 1.6.4 release.
Jincheng, if you want to be the release manager, I'm happy to assist you
with my PMC powers :)
On Mon, Feb 11, 2019 at 1:24 PM Till Rohrmann wrote:
> Hi Jincheng,
>
> releasing a new bug fix release for the 1.6.x series is a really good idea
> since it already contains a
Jiangjie Qin created FLINK-11576:
Summary: Standardize connector metrics
Key: FLINK-11576
URL: https://issues.apache.org/jira/browse/FLINK-11576
Project: Flink
Issue Type: New Feature
Hi Jincheng,
releasing a new bug fix release for the 1.6.x series is a really good idea
since it already contains a couple of important fixes. Do you want to be
the release manager for this release?
Cheers,
Till
On Mon, Feb 11, 2019 at 1:03 PM jincheng sun
wrote:
> Thanks Gordon to create the
Hi folks,
I would like to start the FLIP discussion thread about standardize the
connector metrics.
In short, we would like to provide a convention of Flink connector metrics.
It will help simplify the monitoring and alerting on Flink jobs. The FLIP
link is following:
Thanks Gordon to create the first release candidate for 1.7.2.
It has been a long time since the release of 1.6.3 (December 23, 2018).
There have been a lot of valuable bug fixes during this period. Do we need
to release 1.6.4?
Cheers,
Jincheng
Tzu-Li (Gordon) Tai 于2019年2月11日周一 下午5:06写道：
>
Hi Shaoxuan,
Thank you for your feedback.
If the author is not familiar with Chinese, he/she should create a
translation JIRA before the pull request is merged in.
The created JIRA can be attached a "chinese-translation" tag so that it can
be searched easily. Then a Chinese contributor can take
>
> We can also try to assign documentation components to both "Documentation"
> and the affected component, such as "Runtime / Metrics".
This is critical for anyone trying to keep an eye on the documentation as a
whole -- e.g., ensuring that it remains readable, is well-organized, and is
being
Thanks a lot for your feedback!
@Timo:
I've followed your suggestions and updated the proposed names in the wiki.
Regarding a new "SQL/Connectors" component: I (with admittedly not much
knowledge) would not add this component at the moment, and put the SQL
stuff into the respective connector
Hey,
I added you to our JIRA.
On Mon, Feb 11, 2019 at 8:16 AM shengjk1 wrote:
> Hi Guys,
>
> Could anyone give me the contributor permission ?
>
>
> My Jira ID is shengjk1
>
>
>
>
> thanks
>
>
Thanks. I'll proceed to create the first release candidate for 1.7.2 now
then.
On Mon, Feb 11, 2019 at 3:55 PM Till Rohrmann wrote:
> FLINK-10868 needs another round of reviews. At the moment, I cannot make
> any guarantees until when this will happen and therefore I would suggest to
> not
I like the idea of maintaining an up-to-date long term roadmap for Flink.
And the roadmap should reflect the users' wishes to Flink. I remember Flink
did collected users' feedbacks some years ago but I could not find the
links right now -- we could use them or a newer version as the starting
point
Thanks for the feedback, Shaoxuan.
I'll create a FLIP then. Good point about documentation. I'll put together
a doc on the website once we agreed upon the detail metric specifications.
Jiangjie (Becket) Qin
On Mon, Feb 11, 2019 at 4:10 PM Shaoxuan Wang wrote:
> Becket,
>
> Thanks for the
Kostas Kloudas created FLINK-11574:
--
Summary: Make StreamTask properly handle the DRAIN message.
Key: FLINK-11574
URL: https://issues.apache.org/jira/browse/FLINK-11574
Project: Flink
Issue
I agree with what was said above. I think that announcing a release manager
at the beginning of the release cycle is beneficial. The release manager
could help with several tasks which help improving the release process if
done continuously:
1. Tracking progress of features and posting updates to
Kostas Kloudas created FLINK-11575:
--
Summary: Let the JobManager send the SUSPEND and DRAIN messages
Key: FLINK-11575
URL: https://issues.apache.org/jira/browse/FLINK-11575
Project: Flink
Kostas Kloudas created FLINK-11573:
--
Summary: Make StreamTask properly handle the SUSPEND message.
Key: FLINK-11573
URL: https://issues.apache.org/jira/browse/FLINK-11573
Project: Flink
Kostas Kloudas created FLINK-11572:
--
Summary: Add new types of CheckpointBarriers.
Key: FLINK-11572
URL: https://issues.apache.org/jira/browse/FLINK-11572
Project: Flink
Issue Type:
Becket,
Thanks for the proposal. I am much agree that we should only design the
standard/common Flink-related connector metrics, while keep the original
names for the ones provided by the connector itself. If everyone agrees to
make these changes, we should do it asap, the earlier to make the
Thanks so much Timo.
Adding the ServicesResourceTransformer solved my problem.
Regards,
~Ramya.
On Wed, Feb 6, 2019 at 9:48 PM Timo Walther wrote:
> Hi Ramya,
>
> at the first glance your pom.xml looks correct. What is the contents of
>
Hi,
I am making use of Flink SQL for processing my data.
And I would like to compute TOP counts, for many of the parameters in a row.
Is there any better way to do this as i can see that LIMIT is not supported
in Batch Queries.
Any help is appreciated.
Thanks,
39 matches
Mail list logo
