[
https://issues.apache.org/jira/browse/OAK-11735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953337#comment-17953337
]
Thomas Mueller edited comment on OAK-11735 at 5/22/25 6:37 AM:
---------------------------------------------------------------
PR https://github.com/apache/jackrabbit-oak/pull/2302
was (Author: tmueller):
PR https://github.com/apache/jackrabbit-oak/compare/OAK-11735?expand=1
> Index merge: merge aggregation definitions
> ------------------------------------------
>
> Key: OAK-11735
> URL: https://issues.apache.org/jira/browse/OAK-11735
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
>
> The ["aggregates"
> definitions|https://jackrabbit.apache.org/oak/docs/query/lucene.html#aggregation]
> are not currently merged. If both the product as well as the customization
> have new entries, then they will conflict, because they have the same node
> name (eg. include11). (JCR does not support arrays of objects like JSON,
> that's why we have these names).
> To resolve this, the newly added customizations need to be renamed. Eg.
> {noformat}
> ancestor:
> /oak:index/acme-1
> aggregates/asset/include1/a
> customization:
> /oak:index/acme-1-custom-2
> aggregates/asset/include1/a
> aggregates/asset/include2/xyz <== conflict due to name "include2"
> new product:
> /oak:index/acme-2
> aggregates/asset/include1/a
> aggregates/asset/include2/b <== conflict due to name "include2"
> expected:
> /oak:index/acme-2
> aggregates/asset/include1/a
> aggregates/asset/include2/b <== copy from product
> aggregates/asset/include3/xyz <== rename "include2" -> "include3"
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
