You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Fabrizio Fortino (Jira)" <ji...@apache.org> on 2020/07/26 08:54:00 UTC

[jira] [Created] (OAK-9155) oak-search-elastic: remove :fulltext field

Fabrizio Fortino created OAK-9155:
-------------------------------------

             Summary: oak-search-elastic: remove :fulltext field
                 Key: OAK-9155
                 URL: https://issues.apache.org/jira/browse/OAK-9155
             Project: Jackrabbit Oak
          Issue Type: Task
          Components: elastic-search, oak-search
            Reporter: Fabrizio Fortino
            Assignee: Fabrizio Fortino


While executing the full-text performance benchmarks, where we import a Wikipedia dump into the repository, I have noticed we copy the value of analyzed/nodeScopeIndexed fields into the :fulltext field. AFAIK this is mainly used for full-text queries with a clause like:
{code:java}
contains(., "some text"){code}
The proposal is to remove the :fulltext field completely and for queries clauses like above we can use a multi-match query with cross_fields type [0].

This will impact in a good way the configuration: in lucene a reindex is needed when a property is set to nodeScopeIndex=true. In elastic the reindex won't be needed because the fields for the multi-match query are dynamic.

[0] [https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html#type-cross-fields]



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