[jira] [Updated] (OAK-7261) DocumentStore: inconsistent behaviour for invalid Strings as document ID

["Julian Reschke (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-7261:
--------------------------------
    Fix Version/s:     (was: 1.16.0)
                   1.18.0

> DocumentStore: inconsistent behaviour for invalid Strings as document ID
> ------------------------------------------------------------------------
>
>                 Key: OAK-7261
>                 URL: https://issues.apache.org/jira/browse/OAK-7261
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk, mongomk, rdbmk
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>             Fix For: 1.18.0
>
>
> - H2DB and Derby roundtrip any string
>  - PostgreSQL rejects the invalid string early
>  - DB2 and Oracle fail the same way as segment store (they persist the replacement character) (see OAK-5506)
>  - MySQL and SQLServer fail the same way as DB2 and Oracle, but here it's the RDBDocumentStore's fault, because the ID column is binary, and we transform to byte sequences ourselves
>  - Mongo claims it saved the document, but upon lookup, returns something with a different ID
> Note that due to how RDB reads work, the returned document has the ID that was requested, not what the DB actually contains.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)