You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2018/02/23 13:23:00 UTC

[jira] [Commented] (OAK-7281) DocumentStore: long path handling looses information when strings are invalid

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

Julian Reschke commented on OAK-7281:
-------------------------------------

https://issues.apache.org/jira/secure/attachment/12911721/OAK-7281.diff modifies {{Utils}} to use the non-permissive encoder, and also takes advantage of not having to create byte arrays everywhere.

> DocumentStore: long path handling looses information when strings are invalid
> -----------------------------------------------------------------------------
>
>                 Key: OAK-7281
>                 URL: https://issues.apache.org/jira/browse/OAK-7281
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>            Reporter: Julian Reschke
>            Priority: Minor
>         Attachments: OAK-7281.diff
>
>
> The various methods related to long paths in {{org.apache.jackrabbit.oak.plugins.document.util.Utils}} use {{String.getBytes()}} which will map invalid inputs to the same replacement character. Thus multiple long paths might map to the same hash.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)