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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/05/19 11:55:59 UTC

[jira] [Updated] (OAK-2890) SegmentBlob does not return blobId for contentIdentity

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

Chetan Mehrotra updated OAK-2890:
---------------------------------
    Attachment: OAK-2890.patch

[patch|^OAK-2890.patch] for the same

[~alex.parvulescu] [~tmueller] Can you review the patch. Its a small fix but just want to be sure here

> SegmentBlob does not return blobId for contentIdentity
> ------------------------------------------------------
>
>                 Key: OAK-2890
>                 URL: https://issues.apache.org/jira/browse/OAK-2890
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segmentmk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.3.0, 1.2.3, 1.0.15
>
>         Attachments: OAK-2890.patch
>
>
> {{SegmentBlob}} currently returns recordId for {{contentIdentity}} even when an external DataStore is configured. Given that recordId is not stable it would be better to return the blobId as part of  {{contentIdentity}} if external DataStore is configured



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)