Error with Flink-Gelly, lastJobExecutionResult is null

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Error with Flink-Gelly, lastJobExecutionResult is null

Xia Rui
Hello, everyone.

I am using Flink-Gelly. I got an error when running the example code of
Gelly-example. I have reported the problem in Stackoverflow, and this is the
link
(https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
executionresult-is-null-for-executionenvironment)

 

I am trying to figure out the error point. I traced the env.execute()
function, and it is actually invoked in ContextEnvironment::execute() (link:
https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/
apache/flink/client/program/ContextEnvironment.java#L71). In fact, the
variable lastJobExecutionResult (from ContextEnvironment's super class
ExecutionEnvironment) is not set.

 

I checked the history of ContextEnvironment, and find that
lastJobExecutionResult is exclude from ClusterClient in FLINK-14456
(https://issues.apache.org/jira/browse/FLINK-14456). This is merged to
master after flink-1.10.

 

I was wondering If I could set the lastJobExecutionResult in
ContextEnvironment::execute() for my case (run Flink-Gelly on flink >= 1.10)
without significant side effect.

 

Thank you.

Reply | Threaded
Open this post in threaded view
|

Re: Error with Flink-Gelly, lastJobExecutionResult is null

Till Rohrmann
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
correctly. I'm pulling in Aljoscha, Klou and Tison who worked on this
feature. I believe they can propose a fix for the problem.

[1] https://issues.apache.org/jira/browse/FLINK-15116

On Sun, Aug 2, 2020 at 11:28 AM Xia Rui <[hidden email]> wrote:

> Hello, everyone.
>
> I am using Flink-Gelly. I got an error when running the example code of
> Gelly-example. I have reported the problem in Stackoverflow, and this is
> the
> link
> (
> https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
> executionresult-is-null-for-executionenvironment
> <https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjobexecutionresult-is-null-for-executionenvironment>
> )
>
>
>
> I am trying to figure out the error point. I traced the env.execute()
> function, and it is actually invoked in ContextEnvironment::execute()
> (link:
>
> https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/
> apache/flink/client/program/ContextEnvironment.java#L71
> <https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/apache/flink/client/program/ContextEnvironment.java#L71>).
> In fact, the
> variable lastJobExecutionResult (from ContextEnvironment's super class
> ExecutionEnvironment) is not set.
>
>
>
> I checked the history of ContextEnvironment, and find that
> lastJobExecutionResult is exclude from ClusterClient in FLINK-14456
> (https://issues.apache.org/jira/browse/FLINK-14456). This is merged to
> master after flink-1.10.
>
>
>
> I was wondering If I could set the lastJobExecutionResult in
> ContextEnvironment::execute() for my case (run Flink-Gelly on flink >=
> 1.10)
> without significant side effect.
>
>
>
> Thank you.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Error with Flink-Gelly, lastJobExecutionResult is null

Aljoscha Krettek-2
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 since with other ExecutionEnvironments, we still set the field
> correctly. I'm pulling in Aljoscha, Klou and Tison who worked on this
> feature. I believe they can propose a fix for the problem.
>
> [1] https://issues.apache.org/jira/browse/FLINK-15116
>
> On Sun, Aug 2, 2020 at 11:28 AM Xia Rui <[hidden email]> wrote:
>
>> Hello, everyone.
>>
>> I am using Flink-Gelly. I got an error when running the example code of
>> Gelly-example. I have reported the problem in Stackoverflow, and this is
>> the
>> link
>> (
>> https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
>> executionresult-is-null-for-executionenvironment
>> <https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjobexecutionresult-is-null-for-executionenvironment>
>> )
>>
>>
>>
>> I am trying to figure out the error point. I traced the env.execute()
>> function, and it is actually invoked in ContextEnvironment::execute()
>> (link:
>>
>> https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/
>> apache/flink/client/program/ContextEnvironment.java#L71
>> <https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/apache/flink/client/program/ContextEnvironment.java#L71>).
>> In fact, the
>> variable lastJobExecutionResult (from ContextEnvironment's super class
>> ExecutionEnvironment) is not set.
>>
>>
>>
>> I checked the history of ContextEnvironment, and find that
>> lastJobExecutionResult is exclude from ClusterClient in FLINK-14456
>> (https://issues.apache.org/jira/browse/FLINK-14456). This is merged to
>> master after flink-1.10.
>>
>>
>>
>> I was wondering If I could set the lastJobExecutionResult in
>> ContextEnvironment::execute() for my case (run Flink-Gelly on flink >=
>> 1.10)
>> without significant side effect.
>>
>>
>>
>> Thank you.
>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: Error with Flink-Gelly, lastJobExecutionResult is null

Robert Metzger
Does this mean this is a valid issue?
If so, we could track it as a starter issue?

On Mon, Aug 3, 2020 at 10:59 AM Aljoscha Krettek <[hidden email]>
wrote:

> 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 since with other ExecutionEnvironments, we still set the
> field
> > correctly. I'm pulling in Aljoscha, Klou and Tison who worked on this
> > feature. I believe they can propose a fix for the problem.
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-15116
> >
> > On Sun, Aug 2, 2020 at 11:28 AM Xia Rui <[hidden email]> wrote:
> >
> >> Hello, everyone.
> >>
> >> I am using Flink-Gelly. I got an error when running the example code of
> >> Gelly-example. I have reported the problem in Stackoverflow, and this is
> >> the
> >> link
> >> (
> >>
> https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjob
> >> executionresult-is-null-for-executionenvironment
> >> <
> https://stackoverflow.com/questions/63211746/error-with-flink-gelly-lastjobexecutionresult-is-null-for-executionenvironment
> >
> >> )
> >>
> >>
> >>
> >> I am trying to figure out the error point. I traced the env.execute()
> >> function, and it is actually invoked in ContextEnvironment::execute()
> >> (link:
> >>
> >>
> https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/
> >> apache/flink/client/program/ContextEnvironment.java#L71
> >> <
> https://github.com/apache/flink/blob/master/flink-clients/src/main/java/org/apache/flink/client/program/ContextEnvironment.java#L71
> >).
> >> In fact, the
> >> variable lastJobExecutionResult (from ContextEnvironment's super class
> >> ExecutionEnvironment) is not set.
> >>
> >>
> >>
> >> I checked the history of ContextEnvironment, and find that
> >> lastJobExecutionResult is exclude from ClusterClient in FLINK-14456
> >> (https://issues.apache.org/jira/browse/FLINK-14456). This is merged to
> >> master after flink-1.10.
> >>
> >>
> >>
> >> I was wondering If I could set the lastJobExecutionResult in
> >> ContextEnvironment::execute() for my case (run Flink-Gelly on flink >=
> >> 1.10)
> >> without significant side effect.
> >>
> >>
> >>
> >> Thank you.
> >>
> >>
> >
>
>