[
https://issues.apache.org/jira/browse/OAK-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-1852:
--------------------------------
Description:
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)
was:
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?
> 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
> Assignee: Thomas Mueller
> Priority: Minor
> 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.3.4#6332)
