Not sure, because there's going to be two WindwoOperator classes on the
class path when deserialising this on the cluster.

On Mon, 14 Nov 2016 at 10:07 Ufuk Celebi <u...@apache.org> wrote:

> On 11 November 2016 at 18:19:30, Aljoscha Krettek (aljos...@apache.org)
> wrote:
> > Hi,
> > I think the jar files in the lib folder are checked first so shipping the
> > WindowOperator with the job should not work.
>
> The WindowOperator is instantiated on the client side and shipped as user
> code to the cluster, so it should be OK to only have the modified
> WindowOperator code locally.
>
> That should work, Aljoscha? Or am I overlooking something here.
>
> – Ufuk
>
>
>

Reply via email to