Hi Dan,
in my experience this kind of errors are caused by some other problem
that's not immediately obvious (like some serialization, memory or RocksDB
problem).
Could it be that an Avro field cannot be null or viceversa?
On Tue, Dec 21, 2021 at 7:21 PM Dan Hill wrote:
> I was not able to repro
I was not able to reproduce it by re-running the same job with an updated
kryo library. The join doesn't do anything special.
On Sun, Dec 19, 2021 at 4:58 PM Dan Hill wrote:
> I'll retry the job to see if it's reproducible. The serialized state is
> bad so that run keeps failing.
>
> On Sun, De
I'll retry the job to see if it's reproducible. The serialized state is bad
so that run keeps failing.
On Sun, Dec 19, 2021 at 4:28 PM Zhipeng Zhang
wrote:
> Hi Dan,
>
> Could you provide the code snippet such that we can reproduce the bug here?
>
> Dan Hill 于2021年12月20日周一 07:18写道：
>
>> Hi.
>>
Hi Dan,
Could you provide the code snippet such that we can reproduce the bug here?
Dan Hill 于2021年12月20日周一 07:18写道：
> Hi.
>
> I was curious if anyone else has hit this exception. I'm using the
> IntervalJoinOperator to two streams of protos. I registered the protos
> with a kryo serializer.
Hi.
I was curious if anyone else has hit this exception. I'm using the
IntervalJoinOperator to two streams of protos. I registered the protos
with a kryo serializer. I started hitting this issue which looks like the
operator is trying to deserialize a bad set of bytes that it serialized.
I'm no
