FullText index can't be disabled for cache with String values.

[Andrew Mashenkov]

Igniters,

I've found that we can't use SORTED index only for cache with String
values.
FULLTEXT index has always being created in
IgniteH2Indexing.TableDescriptor.createIndexes().

I've create a ticket IGNITE-4715 [1]. Serji, please, take a look at this.

[1] https://issues.apache.org/jira/browse/IGNITE-4715

--
Best regards,
Andrey V. Mashenkov

[Sergi]

Yes, this looks like a bad decision from the old times. I guess by default
we should not create fulltext index for String, it must be explicitly
enabled in QueryEntity if needed.

Sergi

2017-02-17 10:18 GMT+03:00 Andrey Mashenkov <[hidden email]>:

> Igniters,
>
> I've found that we can't use SORTED index only for cache with String
> values.
> FULLTEXT index has always being created in
> IgniteH2Indexing.TableDescriptor.createIndexes().
>
> I've create a ticket IGNITE-4715 [1]. Serji, please, take a look at this.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4715
>
> --
> Best regards,
> Andrey V. Mashenkov
>

[dsetrakyan]

I have added a newbie label to this ticket. I think it should be simple
enough to address.

On Fri, Feb 17, 2017 at 12:05 AM, Sergi Vladykin <[hidden email]>
wrote:

> Yes, this looks like a bad decision from the old times. I guess by default
> we should not create fulltext index for String, it must be explicitly
> enabled in QueryEntity if needed.
>
> Sergi
>
> 2017-02-17 10:18 GMT+03:00 Andrey Mashenkov <[hidden email]>:
>
> > Igniters,
> >
> > I've found that we can't use SORTED index only for cache with String
> > values.
> > FULLTEXT index has always being created in
> > IgniteH2Indexing.TableDescriptor.createIndexes().
> >
> > I've create a ticket IGNITE-4715 [1]. Serji, please, take a look at this.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4715
> >
> > --
> > Best regards,
> > Andrey V. Mashenkov
> >
>