Re: [ANNOUNCE] Contributing Alibaba's Blink

Glad to see this announcement, I already heard of many users asking the time of Blink open source in China recently, and thanks Stephan for making this happen. All the enhancements or features in Blink would be eventually contirbuted/merged into Flink in more fine-grained way finally. Before

[jira] [Created] (FLINK-11411) Failover regions number of RestartPipelinedRegionStrategy not show in LOG due to incorrect parameter

BoWang created FLINK-11411: -- Summary: Failover regions number of RestartPipelinedRegionStrategy not show in LOG due to incorrect parameter Key: FLINK-11411 URL: https://issues.apache.org/jira/browse/FLINK-11411

[Feature]Returning RuntimeException to REST client while job submission

Hello, The change in FLINK-10312 makes REST response of the API not very informative. It strips the stack trace and returns a generic message. People

Request for permission

Hi Guys, I want to contribute to Apache Flink. Would you please give me the permission as a contributor? My JIRA ID is fan_li_ya. Thanks a lot. Best, Liya Fan

Re: [Feature]Returning RuntimeException to REST client while job submission

Or maybe I am missing something? It looks like the JIRA is trying to solve the same issues I stated 樂 In the main method, I just threw a simple new Exception("Some message") and I got the response I mentioned from the rest API. Thanks. On Wed, Jan 23, 2019 at 2:50 PM Lavkesh Lahngir wrote: >

[DISCUSS] Shall we make SpillableSubpartition repeatedly readable to support fine grained recovery

Hi all, When running the batch WordCount example, I configured the job execution mode as BATCH_FORCED, and failover-strategy as region, I manually injected some errors to let the execution fail in different phases. In some cases, the job could recovery from failover and became succeed, but in

Re: [ANNOUNCE] Contributing Alibaba's Blink

Hi all, @Stephan Thanks a lot for driving these efforts. I think a lot of people is already waiting for this. +1 for opening the blink source code. Both a separate repository or a special branch is ok for me. Hopefully, this will not last too long. Best, Hequn On Tue, Jan 22, 2019 at 11:35 PM

Re: Issues regarding Table-API

Hi Elias, For your question 2: this is doable, i think it will be resolved in future version of Flink. Best, Kurt On Tue, Jan 15, 2019 at 10:35 PM Elias Saalmann < es45g...@studserv.uni-leipzig.de> wrote: > Hi there, > > I'm working on the Gradoop project at the University of Leipzig ( >

Re: [DISCUSS] A strategy for merging the Blink enhancements

Hi Stephan, Thanks for bringing up the discussions. I'm +1 on the merging plan. One question though: since the merge will not be completed for some time and there are might be uses trying blink branch, what's the plan for the development in the branch? Personally I think we may discourage big

[jira] [Created] (FLINK-11410) Kubernetes Setup page gives incorrect url of Flink UI

Frank Huang created FLINK-11410: --- Summary: Kubernetes Setup page gives incorrect url of Flink UI Key: FLINK-11410 URL: https://issues.apache.org/jira/browse/FLINK-11410 Project: Flink Issue

[jira] [Created] (FLINK-11409) Make `ProcessFunction`, `ProcessWindowFunction` and etc. pure interfaces

Kezhu Wang created FLINK-11409: -- Summary: Make `ProcessFunction`, `ProcessWindowFunction` and etc. pure interfaces Key: FLINK-11409 URL: https://issues.apache.org/jira/browse/FLINK-11409 Project: Flink

Flink CEP : Doesn't generate output

Hi All, I have used Flink CEP to filter some events and generate some alerts based on certain conditions. But unfortunately doesn't print any result. I have attached source code herewith, could you please help me on this. package

[jira] [Created] (FLINK-11408) ContinuousProcessingTimeTrigger: NPE on clear() and state is lost on merge

Cristian created FLINK-11408: Summary: ContinuousProcessingTimeTrigger: NPE on clear() and state is lost on merge Key: FLINK-11408 URL: https://issues.apache.org/jira/browse/FLINK-11408 Project: Flink

[jira] [Created] (FLINK-11407) Allow providing reason messages for TypeSerializerSchemaCompatibility.incompatible()

Tzu-Li (Gordon) Tai created FLINK-11407: --- Summary: Allow providing reason messages for TypeSerializerSchemaCompatibility.incompatible() Key: FLINK-11407 URL:

[jira] [Created] (FLINK-11406) Return TypeSerializerSchemaCompatibility.incompatible() when arity of nested serializers don't match in CompositeTypeSerializerSnapshot's compatibility check

Tzu-Li (Gordon) Tai created FLINK-11406: --- Summary: Return TypeSerializerSchemaCompatibility.incompatible() when arity of nested serializers don't match in CompositeTypeSerializerSnapshot's compatibility check Key:

Re: [ANNOUNCE] Contributing Alibaba's Blink

Great news! Looking forward to the new wave of developments. If Blink needs to be continuously updated, fix bugs, release versions, maybe a separate repository is a better idea. Best, Jark On Tue, 22 Jan 2019 at 18:29, Dominik Wosiński wrote: > Hey! > I also think that creating the separate

[DISCUSS] Start new Review Process

Hi everyone, A few months ago the community discussed and agreed to improve the PR review process [1-4]. The idea is to follow a checklist to avoid in-depth reviews on contributions that might not be accepted for other reasons. Thereby, reviewers and contributors do not spend their time on PRs

[DISCUSS] A strategy for merging the Blink enhancements

Dear Flink community! As a follow-up to the thread announcing Alibaba's offer to contribute the Blink code [1] , here are some thoughts on how this contribution could be

Re: Apply for Flink contributor permission

HI Hongtao, Welcome to the Flink community! I gave you contributor permissions for Jira. Best, Fabian Am Di., 22. Jan. 2019 um 07:04 Uhr schrieb 张洪涛 : > Hi Guys, > > Could anyone give me the contributor permission ? > > My Jira ID is hongtao12310 > > Regards, > Hongtao >

Re: [ANNOUNCE] Contributing Alibaba's Blink

Hey! I also think that creating the separate branch for Blink in Flink repo is a better idea than creating the fork as IMHO it will allow merging changes more easily. Best Regards, Dom. wt., 22 sty 2019 o 10:09 Ufuk Celebi napisał(a): > Hey Stephan and others, > > thanks for the summary. I'm

Re: [ANNOUNCE] Contributing Alibaba's Blink

Hey Stephan and others, thanks for the summary. I'm very excited about the outlined improvements. :-) Separate branch vs. fork: I'm fine with either of the suggestions. Depending on the expected strategy for merging the changes, expected number of additional changes, etc., either one or the

Re: [ANNOUNCE] Contributing Alibaba's Blink

Thanks Stephan! This is a very exciting news for the flink community. I recommend creating a branch for blink in the Flink repository. Just like feature development, the blink branch is a branch with many enhancements, and the enhanced functionality is continuously merged to the flink master.

Re: [ANNOUNCE] Contributing Alibaba's Blink

Thanks for driving these efforts, Stephan! Great news that the Blink code base will be available for everyone soon. I already got access to it and the added functionality and improved architecture is impressive. There will be nice additions to Flink. I guess the Blink code base will be

Re: [ANNOUNCE] Contributing Alibaba's Blink

Hi Driesprong, Glad to hear that you're interested with blink's codes. Actually, blink only has one branch by itself, so either a separated repo or a flink's branch works for blink's code share. Best, Kurt On Tue, Jan 22, 2019 at 2:30 PM Driesprong, Fokko wrote: > Great news Stephan! > > Why