You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Alexey Kuznetsov <ak...@gridgain.com> on 2015/06/02 17:43:48 UTC
Re: SQL query question
After investigation this issue I found the following:
It seems that we have here a special case of Scala and Java compatibility.
In Scala it is possible to use "Int" to work with cache, and actually "Int"
in Scala compiled into primitive "int". But in Java we can not use
primitives as cache keys we could only use objects.
But also in your code you registered indexed types and Scala "Int" was taken
as primitive "int".
And when you try to insert into cache boxing take place and "Integer" type
used to update indexes.
So, I think we could handle this inside Ignite by translating primitive
types to corresponding
object types in CacheCfg.setIndexedTypes(...) method.
I created https://issues.apache.org/jira/browse/IGNITE-983 for this.
For now you could use java.lang.Integer.
Or fix IGNITE-983 (I think it will be trivial).
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-query-question-tp426p447.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: SQL query question
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Ognen,
I fixed it already.
Fix is simple - translate primitive types to object types.
Pushed fix to ignite-983 branch.
If all tests passed on TC it will be merged into sprint-5 and will be
available in next upcoming release.
On Wed, Jun 3, 2015 at 8:09 AM, Ognen Duzlevski <og...@gmail.com>
wrote:
> Aleksej, I would be happy to give it a whirl if we can take this off list
> and you can give me some pointers :)
> Ognen
>
> On Tue, Jun 2, 2015 at 10:43 AM, Alexey Kuznetsov <akuznetsov@gridgain.com
> > wrote:
>
>> After investigation this issue I found the following:
>>
>> It seems that we have here a special case of Scala and Java compatibility.
>> In Scala it is possible to use "Int" to work with cache, and actually
>> "Int"
>> in Scala compiled into primitive "int". But in Java we can not use
>> primitives as cache keys we could only use objects.
>>
>> But also in your code you registered indexed types and Scala "Int" was
>> taken
>> as primitive "int".
>> And when you try to insert into cache boxing take place and "Integer" type
>> used to update indexes.
>>
>> So, I think we could handle this inside Ignite by translating primitive
>> types to corresponding
>> object types in CacheCfg.setIndexedTypes(...) method.
>>
>> I created https://issues.apache.org/jira/browse/IGNITE-983 for this.
>>
>> For now you could use java.lang.Integer.
>> Or fix IGNITE-983 (I think it will be trivial).
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-ignite-users.70518.x6.nabble.com/SQL-query-question-tp426p447.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: SQL query question
Posted by Ognen Duzlevski <og...@gmail.com>.
Aleksej, I would be happy to give it a whirl if we can take this off list
and you can give me some pointers :)
Ognen
On Tue, Jun 2, 2015 at 10:43 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> After investigation this issue I found the following:
>
> It seems that we have here a special case of Scala and Java compatibility.
> In Scala it is possible to use "Int" to work with cache, and actually "Int"
> in Scala compiled into primitive "int". But in Java we can not use
> primitives as cache keys we could only use objects.
>
> But also in your code you registered indexed types and Scala "Int" was
> taken
> as primitive "int".
> And when you try to insert into cache boxing take place and "Integer" type
> used to update indexes.
>
> So, I think we could handle this inside Ignite by translating primitive
> types to corresponding
> object types in CacheCfg.setIndexedTypes(...) method.
>
> I created https://issues.apache.org/jira/browse/IGNITE-983 for this.
>
> For now you could use java.lang.Integer.
> Or fix IGNITE-983 (I think it will be trivial).
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/SQL-query-question-tp426p447.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>