[
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984812#comment-16984812
]
Thomas Mueller commented on OAK-8783:
-------------------------------------
One problem is that the Gson library doesn't support the child order
https://stackoverflow.com/questions/6365851/how-to-keep-fields-sequence-in-gson-serialization
This is a problem because indexes in Oak do need to respect order of child
nodes for some features:
http://jackrabbit.apache.org/oak/docs/query/lucene.html
"The rules are looked up in the order of there entry under indexRules node
(indexRule node itself is of type nt:unstructured which has orderable child
nodes)" - "Order of property definition node is important as some properties
are based on regular expressions"
Instead of Gson, we need use a different serialization library, e.g. the Oak
JsonObject. I will add the needed features and tests there first.
> Merge index definitions
> -----------------------
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
> Attachments: OAK-8783-v1.patch
>
>
> If there are multiple versions of an index, e.g. asset-2-custom-2 and
> asset-3, then oak-run should be able to merge them to asset-3-custom-1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
