You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by monstereo <me...@gmail.com> on 2018/07/30 08:06:35 UTC

Why thereis a Binary Marshaller?

I have to implement cache in generic way.

Documentation says that "It enables you to construct new objects based on a
type name without having class definitions at all, hence allowing dynamic
type creation."
But when i look at the github examples 
here
<https://github.com/ntikhonov/examples/blob/master/src/main/java/org/apache/ignite/examples/binary/datagrid/CacheClientBinaryPutGetExample.java>  

Where is it that part?
They have followed "type-per-cache pattern". (Cache for organization object,
another cache for person object ....)



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Why thereis a Binary Marshaller?

Posted by vkulichenko <va...@gmail.com>.
The point here is that Ignite stores data in binary format, and
deserialization happens only on client side. Therefore, you can start server
nodes without deploying Person and Organization classes there, and the
example will still work. On top of that, you can change class definition on
client side and rerun the example without restarting server nodes. It would
still work as expected.

More details here: https://apacheignite.readme.io/docs/binary-marshaller

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/