[
https://issues.apache.org/jira/browse/OAK-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789162#comment-16789162
]
Nitin Gupta commented on OAK-8114:
----------------------------------
So In effect -
as of now - I could find these 3 properties whose addition/change shouldn't
require any reindex -
weight and boost values on Property nodes
name value on index node
I have added a patch here [^OAK-8114_1.patch] with failing tests for the above
3 - will start with the implementation now
[~catholicon] , [~tmueller] - can you guys have a quick look at my analysis
around the properties and see if something is wrong in my understanding ?
> 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
> Priority: Major
> Attachments: OAK-8114_1.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)
