Re: OrderedIndex does not comply with JCR's compareTo semantics

2014-08-28 Thread Davide Giannella
On 27/08/2014 14:48, Thomas Mueller wrote: Hi, Could we use a new index type for the new format? For example ordered2 instead of ordered. I know not very creative naming :-) This is a fix to the current index implementation. I think we should stay with the current index. I would prefer if

Re: OrderedIndex does not comply with JCR's compareTo semantics

2014-08-28 Thread Thomas Mueller
Hi, Could we use a new index type for the new format? For example ordered2 instead of ordered. I know not very creative naming :-) This is a fix to the current index implementation. I think we should stay with the current index. Well, we need some way to know whether the data was migrated or

OrderedIndex does not comply with JCR's compareTo semantics

2014-08-27 Thread Davide Giannella
Hello team, as already tracked in https://issues.apache.org/jira/browse/OAK-1763 the ordered index does not comply to JCR's semantics. We start seeing issues in (pre)production around it and therefore I think we need a fix. Unfortunately with the changes of the encoding and algorithm any

Re: OrderedIndex does not comply with JCR's compareTo semantics

2014-08-27 Thread Thomas Mueller
Hi, Could we use a new index type for the new format? For example ordered2 instead of ordered. I know not very creative naming :-) I would prefer if the translation is done automatically on restart or re-index. I woudn't want to install Groovy and / or have to do manual steps if possible.