Igor, As far as I know, we are not going to have a requirement for user classes on the server side. Since the server is not aware about the classes, then method annotations do not make sense anymore.
According to the tickets, the change has been introduced in 2.0, so it was OK to break backward compatibility where necessary. D. On Thu, May 25, 2017 at 10:32 PM, Igor Rudyak <[email protected]> wrote: > Hi guys, > > Does anybody know what's the reason for disabling *@QuerySqlField* and > *@AffinityKeyMapped* annotations on methods in *Ignite 2.1* ? > > Just found two JIRA tickets for this, but there are no details there: > > https://issues.apache.org/jira/browse/IGNITE-5036 > https://issues.apache.org/jira/browse/IGNITE-4950 > > The problem is that this implementation brakes backward compatibility for > previous deployments utilizing Ignite-Cassandra module and POJO classes > using such annotations. > > Igor >
