Re: Ignite to Cassandra change from 1.9 to 2.0

Thanks, Igor. We look forward to the next version coming out. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p13470.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite to Cassandra change from 1.9 to 2.0

There is also patch IGNITE-5368 available which allows you to use annotations for class fields instead of getters/setters. It will be available in the next version of Ignite. -- View this message in context: http://apache-ignite-users.70518

Re: Ignite to Cassandra change from 1.9 to 2.0

Ok, I have finally been able to get back to this. First, I switched the @QuerySqlField annotations back to the fields from the setters as instructed. Then I executed with a minimal persistence settings xml file which only defined the strategy as POJO, but did not specify the field/column combinat

Re: Ignite to Cassandra change from 1.9 to 2.0

First, I do have setters on the class, just didn't include them for space reasons. Second, this is the exact opposite from what I was told originally back January for v1.8. So, this looks like it was a breaking change introduced in v2.0. I haven't checked the latest "what's new" recently. Was t

Re: Ignite to Cassandra change from 1.9 to 2.0

The second problem is that your *HistoryResultKey* doesn't have setters. It will not work without setters - your POJO classes should follow Java Beans convention. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p1

Re: Ignite to Cassandra change from 1.9 to 2.0

First of all - annotations *@QuerySqlField* and *@QueryTextField* are no longer supported for the methods. Because of this simplified persistence descriptor doesn't work as expected. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-

Re: Ignite to Cassandra change from 1.9 to 2.0

I upgraded from Ignite 1.9 to Ignite 2.0 and this started happening. The stacktrace is below. Also, I'm including the .sh script that I'm running so you can see that the only difference between the executions is pointing to v1.9 versus pointing to v2.0. My code didn't change, but it fails in 2.0

Re: Ignite to Cassandra change from 1.9 to 2.0

Could you please provide full exception stack trace? What do you mean by upgraded to version 2.0? Is it Cassandra or Ignite version or something else? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p13108.html Se

Ignite to Cassandra change from 1.9 to 2.0

I've just upgraded to the new version 2.0 from 1.8/1.9 with a Cassandra .xml configuration as the backing data-store. However, v2.0 is failing to pull the column name that's tied to the field name in the persistence definition. Because of that, the CQL being generated is trying to call Cassandra