Re: @QuerySqlField is incompatible in ignite 1.5 with 1.4 when set on method

2015-11-24 Thread Alexey Kuznetsov
Thanks, Alex. Could you tell at what branch you will add this? Will you create an issue that I could track? On Tue, Nov 24, 2015 at 8:59 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > I will add the check for non-get-named method if there are no objections, I > see no reason for not

Re: @QuerySqlField is incompatible in ignite 1.5 with 1.4 when set on method

2015-11-24 Thread Alexey Goncharuk
I will add the check for non-get-named method if there are no objections, I see no reason for not having it. 2015-11-24 13:25 GMT+03:00 Roman Shtykh : > +1 for adding support, particularly because in Scala we don't necessarily > have get... and set... (an underscore can be used for that). > > Rom

Re: @QuerySqlField is incompatible in ignite 1.5 with 1.4 when set on method

2015-11-24 Thread Roman Shtykh
+1 for adding support, particularly because in Scala we don't necessarily have get... and set... (an underscore can be used for that). Roman On Tuesday, November 24, 2015 5:39 PM, Alexey Kuznetsov wrote: Igniters, I have such class in ignite-1.4 class Test( @Id @ScalaCacheQuerySqlField

@QuerySqlField is incompatible in ignite 1.5 with 1.4 when set on method

2015-11-24 Thread Alexey Kuznetsov
Igniters, I have such class in ignite-1.4 class Test( @Id @ScalaCacheQuerySqlField(index = true) val id: Long = 0L, val name: String = null, aStatus: ListStatus, val ruleID: Long = 0L) extends Serializable { private val intStatus = enumToByte(aStatus) @ScalaCacheQuerySqlF