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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2019/06/12 12:41:00 UTC
[jira] [Updated] (OAK-8114) IndexDefinitionBuilder should be
smarter when to reindex while updating a definition
[ https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated OAK-8114:
--------------------------------
Labels: candidate_oak_1_10 candidate_oak_1_6 candidate_oak_1_8 indexingPatch (was: candidate_oak_1_10 candidate_oak_1_6 candidate_oak_1_8)
> IndexDefinitionBuilder should be smarter when to reindex while updating a definition
> ------------------------------------------------------------------------------------
>
> Key: OAK-8114
> URL: https://issues.apache.org/jira/browse/OAK-8114
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene, search
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Major
> Labels: candidate_oak_1_10, candidate_oak_1_6, candidate_oak_1_8, indexingPatch
> Fix For: 1.12.0
>
> Attachments: OAK-8114_1.patch, OAK-8114_2.patch
>
>
> {{IndexDefinitionBuilder}} currently sets reindex flag while building an index definition if there is a difference in existing def v/s what it builds.
> The only place it acts smarter is while setting up nrt or sync flag. There are quite a few properties which only affect querying or cost-estimation and don't imply a change in indexed data. For such cases, simply setting {{refresh=true}} should suffice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)