DefaultSerializer setting only works with *registered* types. You have to have explicit TypeConfiguration for SQL, binary mode, DefaultSerializer, etc to work.
Unregistered types fall back to [Serializable], if it is there, or cause an exception, as you see. Next Ignite version will have dynamic registration [1], but for now, explicit TypeConfiguration is required. [1] https://issues.apache.org/jira/browse/IGNITE-2703 On Wed, Aug 24, 2016 at 11:46 AM, exones <[email protected]> wrote: > Hello, > > Thank you for the clarification. It wasn't clear for me that [Serializable] > was a priority factor when choosing the serializer. But I was asking about > *DefaultSerializer* setting. > Now I removed the [Serializable] attribute and I'm getting another error > (without having explicit TypeConfiguration): > > --- > Exception thrown: 'Apache.Ignite.Core.Binary.BinaryObjectException' in > Apache.Ignite.Core.dll > > Additional information: Unsupported object type > [type=IgniteSerialization.Thing, object=IgniteSerialization.Thing] > --- > > Again: I assume that when you set DefaultSerializer, don't use > [Serializable] attribute and don't set any specific TypeConfiguration for > any type, it should be equivalent to setting TypeConfiguration with this > serializer to *all* types. Otherwise I don't understand what > DefaultSerializer is supposed to represent. Can anyone clarify on that? > > Thank you! > > Alexey Larchenko > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/No-cache-SQL-queries-possible-with- > Default-Serializer-set-to-BinaryReflectiveSerializer-tp7262p7266.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
