Re: Function input type validation

On 09.11.2015 08:49, Aljoscha Krettek wrote: In the case of the TupleTypeInfo subclass it only works because the equals method of TypleTypeInfo is used, IMHO. I've overridden the equals method to check specifically for my implementation and not TupleTypeInfo, implemented a different serializer

Re: Function input type validation

I think this originally comes from the fact that we need to match the input TypeInfo against the generic signature, for example to figure out what "T" means in a MapFunction, T>. That is the reason why Flink can support generic functions even though there is type erasure at

Function input type validation

Hey All, I am wondering what is the reason why Function input types are validated? This might become an issue if the user wants to write his own TypeInfo for a type that flink also handles natively. Let's say I want to implement my own TupleTypeinfo that handles null values, and I pass this

Re: Function input type validation

The reason for input validation is to check if the Function is fully compatible. Actually only the return types are necessary, but it prohibits stupid implementation mistakes and undesired behavior. E.g. if you implement a "class MyMapper extends MapFunction{}" and use it for