[jira] [Commented] (IGNITE-14805) Avoid unconditional Lucene index creation in case of a String value type for a table

["Taras Ledkov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384916#comment-17384916 ] 

Taras Ledkov commented on IGNITE-14805:
---------------------------------------

Taras Ledkov
17 minutes ago
Edited

Dev list discussion.
Looks like we cannot add a simple property and create Lucene index only when the property is enabled.
Because it breaks compatibility. e.g. there were tables with lucene index. Information about lucene index isn’t persisted at the QueryEntity or otherwhere. It is the same case as for the PrimaryKey.

We have to add metadata about all indexes into table configuration (now it is the QueryEntity). And then release we can add property to disable creation by default or add property to CREATE TABLE .. WITH section.

> Avoid unconditional Lucene index creation in case of a String value type for a table
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-14805
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14805
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.10
>            Reporter: Vladimir Pligin
>            Assignee: Taras Ledkov
>            Priority: Major
>
> In the H2TableDescriptor class there's a piece of code:
> {code:java}
> if (type().valueClass() == String.class) {
>     try {
>         luceneIdx = new GridLuceneIndex(idx.kernalContext(), tbl.cacheName(), type);
>     }
>     catch (IgniteCheckedException e1) {
>         throw new IgniteException(e1);
>     }
> }
> {code}
> For most cases it could be avoided.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)