Hi,
thanks a lot for your answers :)
@Timo: sure, I can open an issue, but I'm not sure I understand the problem
to describe it properly. The with() method calls the
getFlatJoinReturnTypes() with the allowMissing parameter set to false. Is
this what you're referring to? What does this parameter d
I checked the code and the MapFunction InitializeWorkSet contains indeed
two instances of type Either. Since we use Java serialization to ship the
operators to the cluster, the MapFunction has to be serializable. Either
you make the Either type serializable or you create these instances in the
open
It seems there is an Either.Left stored somewhere in the Object. Could that be?
> On 28 Nov 2015, at 20:18, Vasiliki Kalavri wrote:
>
> org.apache.flink.util.InstantiationUtil.serializeObject(InstantiationUtil.java:307)
Hi Vasia,
regarding your TypeExtractor problem. The TypeExtractor works correctly.
The with() function of the JoinOperator calls the wrong TypeExtractor
method that does not allow missing type info. This is a bug. Can open an
issue for that?
Regards,
Timo
On 28.11.2015 20:18, Vasiliki Kalav
Hi squirrels,
I have 2 problems with the new Either type and I could use your help to
understand them.
1. I have a piece of code that looks like this:
TypeInformation>> workSetTypeInfo = ...
DataSet>> initialWorkSet =
initialVertices.map(...).returns(workSetTypeInfo);
This gives me the followin
