[
https://issues.apache.org/jira/browse/MINDEXER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965312#comment-17965312
]
Olivier Lamy commented on MINDEXER-68:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#499|https://github.com/apache/maven-indexer/issues/499].
> Align context behaviour in case of replace and merge methods
> ------------------------------------------------------------
>
> Key: MINDEXER-68
> URL: https://issues.apache.org/jira/browse/MINDEXER-68
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 5.1.0
>
>
> Problem is in lack of {{rebuildGroups()}} call in the IndexingContext#replace
> method, while the IndexingContext#merge method invokes the method.
> The invocation in both cases are justified, even if it seems redundant, as in
> both cases after the operation index is modified and various other aspects of
> it are changed (timestamp, descriptor etc).
> The call is redundant in case of "full remote update" case, since the
> transport format does contain these two fields (that are rebuilt by this
> method).
> Still, the fix allows easier Lucene index preparation outside MI and handing
> it over to MI for consumption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
