Chetan Mehrotra created OAK-4789:
------------------------------------
Summary: SegmentBlob should return null contentIdentity for
inlined blobs
Key: OAK-4789
URL: https://issues.apache.org/jira/browse/OAK-4789
Project: Jackrabbit Oak
Issue Type: Improvement
Components: segment-tar, segmentmk
Reporter: Chetan Mehrotra
Priority: Minor
Fix For: 1.6
When a external BlobStore is configured with SegmentNodeStore then blob can
exist in 3 forms
# Blob inlined in segment storage - If blob length is <= 16512 then blob would
be inlined in segment store
# Blob inlined in BlobStore - Most BlobStore implementation also support
inlining of blob content as part of blobId if the size is less than certain
threshold. For {{FileDataStore}} this is determined by {{minRecordLength}}. If
this is less than #1 then such a case would not happen
# Blob whose content are stored in BlobStore without inlining
Currently {{SegmentBlob}} returns recordId for {{getContentIdentity}} call for
inlined blobs. This would cause this value to change if same blob is stored in
a different segmentstore. As discussed
[here|https://issues.apache.org/jira/browse/OAK-4712?focusedCommentId=15476477&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15476477]
this causes ambiguity in certain cases.
Given that {{getContentIdentity}} can return null it would be better if
SegmentBlob returns null for inlined blob.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
