Nice!
On Fri, Nov 7, 2014 at 11:09 PM, Gyula Fóra wrote:
> Okay, I got it working :)
> Turns out I only needed the client from the contextenvironment to get it
> working.
>
> Thanks for the help :)
>
> On Fri, Nov 7, 2014 at 4:26 PM, Aljoscha Krettek
> wrote:
>
> > Ah ok, maybe you can expose m
Okay, I got it working :)
Turns out I only needed the client from the contextenvironment to get it
working.
Thanks for the help :)
On Fri, Nov 7, 2014 at 4:26 PM, Aljoscha Krettek
wrote:
> Ah ok, maybe you can expose methods for direct execution in the
> regular ExecutionEnvironment and then us
Ah ok, maybe you can expose methods for direct execution in the
regular ExecutionEnvironment and then use them from you wrapper.
On Fri, Nov 7, 2014 at 4:18 PM, Gyula Fóra wrote:
> Hey,
>
> Okay, I think this is something that I might be able to use :)
>
> The problem is that the StreamingExecuti
Hey,
Okay, I think this is something that I might be able to use :)
The problem is that the StreamingExecutionEnvironment has nothing to do
with the ExecutionEnvironment (only the name is similar) because we are
completely skipping the optimizer stuff at the execution. And it seemed
that the cont
Hi,
ExecutionEnvironment has a static field contextEnvironment. When you
call getExecutionEnvironment it checks whether this is null. If it is
null it will return a LocalEnvironment, otherwise it will return the
context environment.
In Client.run() the Client creates a ContextEnvironment and calls
Hey Guys,
The .getExecutionEnvironment() method for the StreamingexecutionEnvironment
does not work properly because we always return LocalEnvironment for
running on the minicluster.
I was trying to figure out how to fix this but I got lost in the code
trying to find how you determine whether the
