Perhaps we can put hands on it during the FlinkForward. :-D I have updated
the ticket description finding out that the issue is generated performing a
join just after the cross. See you in Berlin!
saluti,
Stefano
2015-10-06 9:39 GMT+02:00 Till Rohrmann :
> Hi Stefano,
>
>
Hi guys, I could manage to complete the process crossing byte arrays I
deserialize within the group function. However, I think this workaround is
feasible just with relatively simple processes. Any idea/plan about to fix
the serialization problem?
saluti,
Stefano
Stefano Bortoli, PhD
*ENS
Hi Stefano,
we'll definitely look into it once Flink Forward is over and we've finished
the current release work. Thanks for reporting the issue.
Cheers,
Till
On Tue, Oct 6, 2015 at 9:21 AM, Stefano Bortoli wrote:
> Hi guys, I could manage to complete the process crossing
here it is: https://issues.apache.org/jira/browse/FLINK-2800
saluti,
Stefano
2015-10-01 18:50 GMT+02:00 Stephan Ewen :
> This looks to me like a bug where type registrations are not properly
> forwarded to all Serializers.
>
> Can you open a JIRA ticket for this?
>
> On Thu,
Hi guys,
I hit a Kryo exception while running a process 'crossing' POJOs datasets. I
am using the 0.10-milestone-1.
Checking the serializer:
org.apache.flink.api.java.typeutils.runtime.kryo.KryoSerializer.deserialize(KryoSerializer.java:210)
I have noticed that the Kryo instance is reused along
This looks to me like a bug where type registrations are not properly
forwarded to all Serializers.
Can you open a JIRA ticket for this?
On Thu, Oct 1, 2015 at 6:46 PM, Stefano Bortoli wrote:
> Hi guys,
>
> I hit a Kryo exception while running a process 'crossing' POJOs