flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chesnay Schepler <ches...@apache.org>
Subject Re: Custom Serializers
Date Thu, 28 Sep 2017 11:57:33 GMT
On 19.09.2017 11:39, nragon wrote:
> createInstance(Object[] fields) at TupleSerializerBase seems not to be part
> of TypeSerializer API.
> Will I be loosing any functionality? In what cases do you use this instead
> of createInstance()?
>
> // We use this in the Aggregate and Distinct Operators to create instances
> // of immutable Tuples (i.e. Scala Tuples)
>
> Thanks
Taken from TupleSerializerBase:

// We use this in the Aggregate and Distinct Operators to create 
instances // of immutable Tuples (i.e. Scala Tuples) public abstract T 
createInstance(Object[] fields);

On 27.09.2017 17:43, nragon wrote:
> Should I use TypeSerializerSingleton if it is independent of the object which
> it's serializing?
>
>
>
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
>
Generally, use TypeSerializerSingleton. There is virtually no reason to 
not use it. Do keep this section of the TypeSerializer javadoc in mind:

* The methods in this class are assumed to be stateless, such that it is 
effectively thread safe. Stateful * implementations of the methods may 
lead to unpredictable side effects and will compromise both stability 
and * correctness of the program.


Mime
View raw message