Re: CompactingHashTable question

Thanks Fabian! At least now I know the bug is probably not in the driver where I was looking :) On 16 September 2015 at 17:33, Fabian Hueske wrote: > Yes, probing the HashTable with a key that does not exist will yield a join > function call with a null value (or empty iterator in case of CoGrou

Re: CompactingHashTable question

Yes, probing the HashTable with a key that does not exist will yield a join function call with a null value (or empty iterator in case of CoGroup). The semantics of the join are the same regardless of the hash table implementation. The fact that the error only occurs with the managed HT, indicates

Re: CompactingHashTable question

Hi, thanks a lot Fabian! I didn't know that join with the solution set is an outer join. That's a surprise :) So, if I understand correctly, I should have a null value when my other input to the join contains some key that doesn't exist in the solution set, right? That's not the case in my appli

Re: CompactingHashTable question

Hi Vasia, I looked into the code. A serializer should never return null when deserializing. Either it does not detect that something went wrong with the deserialization or it should throw an exception. Regarding the handling of null returns in the Drivers. If there is no entry in the HT for a cer

CompactingHashTable question

Hello to my squirrels, I ran into an NPE for some iterations code and it looks like what's described in FLINK-2443 . I'm trying to understand the problem and I could really use your help :) So far, it seems that the exception is caused by a null v