[jira] [Commented] (OAK-8783) Merge index definitions

2021-06-01 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355081#comment-17355081
 ] 

Thomas Mueller commented on OAK-8783:
-

To merge index definitions:

{noformat}
java -jar oak-run.jar index-diff 
--merge .json 
--merge-add .json 
--target  
--index1 
{noformat}


> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2021-06-01 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355080#comment-17355080
 ] 

Thomas Mueller commented on OAK-8783:
-

http://svn.apache.org/r1890363 (trunk)

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2020-02-19 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17040129#comment-17040129
 ] 

Thomas Mueller commented on OAK-8783:
-

http://svn.apache.org/r1874198 (trunk)

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2020-02-17 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038820#comment-17038820
 ] 

Thomas Mueller commented on OAK-8783:
-

Thanks [~amitjain]! I didn't think about this...

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2020-02-17 Thread Amit Jain (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038791#comment-17038791
 ] 

Amit Jain commented on OAK-8783:


http://svn.apache.org/r1874154 to fix rat check failures.

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2020-02-17 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038181#comment-17038181
 ] 

Thomas Mueller commented on OAK-8783:
-

http://svn.apache.org/r1874107 (trunk).
Review is still welcome.

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2020-02-14 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036858#comment-17036858
 ] 

Thomas Mueller commented on OAK-8783:
-

[~ngupta] [~tihom88] [~fabrizio.fort...@gmail.com] could you please review 
OAK-8783-v2.patch ?

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, OAK-8783-v1.patch, 
> OAK-8783-v2.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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Fabrizio Fortino (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984865#comment-16984865
 ] 

Fabrizio Fortino commented on OAK-8783:
---

[~thomasm] LGTM!

> Merge index definitions
> ---
>
> Key: OAK-8783
> URL: https://issues.apache.org/jira/browse/OAK-8783
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Attachments: OAK-8783-json-1.patch, 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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984861#comment-16984861
 ] 

Thomas Mueller commented on OAK-8783:
-

http://svn.apache.org/r1870584 (trunk) - reviews are still welcome. I also had 
to change the version (from 1.0.1 to 1.1.0).

> 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-json-1.patch, 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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984859#comment-16984859
 ] 

Thomas Mueller commented on OAK-8783:
-

Good point! I will change the newObjectNotRespectingOrder test, so that it 
doesn't expect any specific order.

> 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-json-1.patch, 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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Nitin Gupta (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984846#comment-16984846
 ] 

Nitin Gupta commented on OAK-8783:
--

[~thomasm] - looks good to me .

Just a couple of small comments -

In the test method newObjectRespectingOrder the comment // we expect it's a 
HashMap should be // we expect it's a LinkedHashMap I suppose ?

 

Also , for the test case newObjectNotRespectingOrder, since properties would be 
a plain hashmap here - can we expect it to always return the same result every 
time the test is run ? What I mean to say is, since a hashmap doesn't maintains 
insertion order, wouldn't it be possible that sometimes in the test run it 
might return the correct insertion order too and the test would fail in that 
run ?

> 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-json-1.patch, 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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984815#comment-16984815
 ] 

Thomas Mueller commented on OAK-8783:
-

[~ngupta] [~tihom88] [~fabrizio.fort...@gmail.com] could you please review 
OAK-8783-json-1.patch ?

> 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-json-1.patch, 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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-29 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (OAK-8783) Merge index definitions

2019-11-22 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980259#comment-16980259
 ] 

Thomas Mueller commented on OAK-8783:
-

Attached a first patch (work in progress).

> 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)