[
https://issues.apache.org/jira/browse/OAK-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979417#comment-13979417
]
Davide Giannella commented on OAK-1763:
---------------------------------------
In the index we receive only Strings and [no knowledge of the original
type|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/strategy/IndexStoreStrategy.java#L39].
{code}
IndexStoreStrategy.update(NodeBuilder, String, Set<String>, Set<String>)
{code}
while a proper fix would require an API change that pass down the original type
I could add some heuristic inspection of the value to see if it's a
number/decimal or not and adding therefore padding of
{{[MAX_STRING_LENGTH|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/PropertyIndex.java#L86]}}
{{0s}}.
Would that suit?
> OrderedIndex does not comply with JCR's compareTo semantics
> -----------------------------------------------------------
>
> Key: OAK-1763
> URL: https://issues.apache.org/jira/browse/OAK-1763
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
>
> The ordered index currently uses the lexicographical order of the string
> representation of the values. This does not comply with [JCR's compareTo
> sementics |
> http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.6.5.1%20CompareTo%20Semantics]
> for e.g. double values.
--
This message was sent by Atlassian JIRA
(v6.2#6252)