Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CABuYRcosCXvjQ-fB1xu4O2--yegn_4jodb6TU_NWc3_b4+0yLQ@mail.gmail.com>
References: 
 <CABuYRcosCXvjQ-fB1xu4O2--yegn_4jodb6TU_NWc3_b4+0yLQ@mail.gmail.com>
From: Sergi Vladykin <sergi.vladykin@gmail.com>
Date: Thu, 21 May 2015 09:47:10 +0300
Message-ID: 
 <CA+eZwrHs+vgJnuF0fg639FmDBUsteZgfjsCr-Dyv7kp7rp636w@mail.gmail.com>
Subject: Re: Indexing primitive types
To: dev@ignite.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113f938414d6d2051691ec20

--001a113f938414d6d2051691ec20
Content-Type: text/plain; charset=UTF-8

Current workaround is to create separate class with single annotated
primitive field.

Created issue https://issues.apache.org/jira/browse/IGNITE-930
Will fix it soon.

Sergi

2015-05-21 4:25 GMT+03:00 Valentin Kulichenko <valentin.kulichenko@gmail.com
>:

> Igniters (especially Sergi),
>
> What happens if I use Java primitives like Doubles as values? Are they
> indexed? I just created a simple example which loads some data and executes
> this query: 'select max(_val) from Double'. Indexes are not created and the
> speed of the query is the same as the speed of full cache iteration.
>
> I can't find any configuration properties to tweak this behavior. Also I
> see this in GridQueryProcessor.processAnnotationsInClass() method:
>
> if (U.isJdk(cls))
>     return;
>
> So it looks like all JDK classes are simply ignored. Is this on purpose?
>
> I think primitives should be indexed by default if they are provided in
> CacheConfiguration.setIndexedTypes().
>
> --
> Val
>

--001a113f938414d6d2051691ec20--