Well, in short, you do not need to do any additional steps if you has not explicitly set any other marshaller for your grid.
Ignite uses marshaller to serialize and de-serialize objects. There are different marshallers that Apache Ignite supports. They define format of the serialized objects. In order to be able to de-serialize objects using C++ client BinaryMarshaller should be used. By default if you did not explicitly set some other marshaller BinaryMarshaller is used. You can read more about binary marshaller at the documentation [1]. Also, you should not use withKeepBinary() method as it intended to be used for other purposes and you should not perform any additional steps on C++ client. [1] - https://apacheignite.readme.io/docs/binary-marshaller Best Regards, Igor On Wed, Mar 9, 2016 at 4:34 PM, arthi <[email protected]> wrote: > Thank you! This sounds promising... > > I went through your BinaryMarshaller. If I understand rightly, when I build > the cache in Java, I can place the objects as they are (just that the Pojo > need to be serializable). But, in the C++ client, I will need to invoke the > cache with binary - somthing like - > // Get an instance of binary-enabled cache. > IgniteCache<Integer, BinaryObject> binaryCache = > ignite.cache("myCache").withKeepBinary(); > > am I right ? I also saw my cache entries using visor, and they appear to be > o.a.i.i.binary.BinaryObjectImpl. > > Do you have a sample using C++ API please? I dont see it in the git hub. > > Thanks for all the help, > Arthi > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/C-Client-for-SQL-Queries-tp3407p3418.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
