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 2015/01/05 11:40:34 UTC
[jira] [Updated] (OAK-1852) DocumentStore API: improve
documentation of keys
[ https://issues.apache.org/jira/browse/OAK-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-1852:
--------------------------------
Affects Version/s: 1.0.9
> 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.1.0, 1.0.9
> Reporter: Julian Reschke
> Priority: Minor
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)