Hi Ariel, BinaryMarshaller is used to store data by default. All the data will be stored and sent across the cluster in the Ignite’s binary format. You don’t need to use Serializable since BInaryMarshaller doesn’t rely on the standard Java serialization. Also, there are cases when Ignite will not use BinaryMarshaller and fallback to other mechanisms. These cases are: - If your class implements Externalizable - If your class implements Serializable and defines custom writeObject/readObject methods In these cases to continue using BinaryMarshaller with that class (and you generally want to use BinaryMarshaller everywhere) you need to implement Binarylizable interface.
Stan From: Ariel Tubaltsev Sent: 23 февраля 2018 г. 8:04 To: firstname.lastname@example.org Subject: Does object should implement Serializable? Hi I'm working with regular K,V cache: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html I'm a bit puzzled whether objects that I want to put into cache should implement Serializable. Documentation(https://apacheignite.readme.io/docs/binary-marshaller) says that by default values are stored deserialized. I'm wondering, how then they are passed on the wire, between for example client and server? Does it always use binary marshaller? Thank you Ariel -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/