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/16 12:59:00 UTC

[jira] [Resolved] (OAK-9140) Don't use stored index definition in elastic indexes

     [ https://issues.apache.org/jira/browse/OAK-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabrizio Fortino resolved OAK-9140.
-----------------------------------
    Resolution: Fixed

Committed with revision 1879952.

> Don't use stored index definition in elastic indexes
> ----------------------------------------------------
>
>                 Key: OAK-9140
>                 URL: https://issues.apache.org/jira/browse/OAK-9140
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: indexing
>            Reporter: Amrit Verma
>            Assignee: Fabrizio Fortino
>            Priority: Major
>
> Stored index definitions introduce additional complexities. Also, we are moving in a direction of avoiding index editing/re-indexing. New index definitions instead should be created instead. Re-indexing should be mostly done in case of corrupt indexes (which should not happen in elasticsearch).  Hence we don't see a scenario in which indexed data would be incompatible with index definition, so we don't need stored index definitions for elastic indexes.



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