How will it complicate it? Ignite's binary format can be easily used for storing JSON object, there is nothing in JSON that is not supported by this format. So the flow will be something like this:
1. User wants to store JSON object in the cache. 2. You code parses JSON and uses BinaryObjectBuilder [1] to create a BinaryObject based on JSON data. 3. IgniteCache.put() is called for the BinaryObject. On get() you do inverse conversion. You also get full SQL support and can use EntryProcessor [2] to update individual fields. Will this work? I understand that having native JSON support is more convenient, but it's not in the product yet. And essentially when it's implemented, it will do something similar to what I just described. [1] https://apacheignite.readme.io/docs/binary-marshaller#modifying-binary-objects-using-binaryobjectbuilder [2] https://apacheignite.readme.io/docs/jcache#entryprocessor -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/do-you-support-json-based-cache-tp4160p4230.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
