[
https://issues.apache.org/jira/browse/OAK-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281938#comment-16281938
]
Julian Reschke commented on OAK-1852:
-------------------------------------
"For keys, the maximum length is 512 bytes in the UTF-8 representation (in the
latest Unicode version)."
That's a bit misleading, as the UTF-8 representation is independent of the
Unicode version - [~mreutegg], [~tmueller]: maybe just remove the "(in the
latest Unicode version)"??
> DocumentStore API: improve documentation of keys
> ------------------------------------------------
>
> Key: OAK-1852
> URL: https://issues.apache.org/jira/browse/OAK-1852
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: doc, mongomk
> Affects Versions: 1.0.9, 1.1.0
> Reporter: Julian Reschke
> Assignee: Thomas Mueller
> Fix For: 1.2
>
>
> I think it would be good to enhance the documentation on what syntactical
> constraints there are on keys.
> For instance:
> - what character range is allowed? what about control characters?
> - is leading or trailing whitespace allowed?
> - are there any assumptions about Unicode normalization on lookup?
> - are keys opaque strings? for instance, does the "/" character have any
> *special* role? will all keys have the "n:" prefix?
> - what length needs to be supported? (MySQL has a limit on 767/4 characters
> because of UTF8-to-octet mapping)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
