Valya, Regarding *IGNITE-2100*. For now in case of Externalizable class we delegate to OptimizedMarshaller, which is more or less fine I think.
Several solutions possible: 1) In case an attempt to read a field of such object is performed, we can throw an exception with workaround in message. Workarounds could be: - Implement Binarizable interface for this class. Problem: sometimes user cannot change class. - Introducee BinarySerializer for this type and add it to configuration. Problem: boilerplate code, public field getters are required. 2) Deserialize such object and use reflection to get field. This is the most user-friendly solution, but will require more time due to changes in cache/query logic. Thoughts? Vladimir. On Tue, Dec 8, 2015 at 1:50 PM, Alexey Goncharuk <[email protected] > wrote: > While checking the Proxy test, I discovered another issue with > BinaryMarshaller: > https://issues.apache.org/jira/browse/IGNITE-2104 > > Even though it is not as critical as the other three mentioned by Val, it > would be nice to get it fixed in 1.5-GA. >
