jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1852) DocumentStore API: improve documentation of keys
Date Wed, 02 Jul 2014 17:43:24 GMT

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

Julian Reschke commented on OAK-1852:
-------------------------------------

Note that this is important because relational databases do not support arbitrarily wide primary
keys. In many cases, their limits are counted in bytes, not characters, so the presence of
non-ASCII characters in a key would make the effective id wider than obvious.

> 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
>            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.2#6252)

Mime
View raw message