jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8314) BlobIds created with direct uploads lack length suffix
Date Wed, 15 May 2019 10:09:00 GMT

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

Amit Jain commented on OAK-8314:

[~mattvryan] No, the IT for DSGC does not use a fixture for the document node store, see [1].
Not sure why it was excluded since, the parent class does have that. Or is there another test

[1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/test/java/org/apache/jackrabbit/oak/jcr/binary/BinaryAccessDSGCIT.java#L89-L90

> BlobIds created with direct uploads lack length suffix
> ------------------------------------------------------
>                 Key: OAK-8314
>                 URL: https://issues.apache.org/jira/browse/OAK-8314
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: blob-plugins
>    Affects Versions: 1.12.0, 1.10.2
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>            Priority: Blocker
>             Fix For: 1.10.3, 1.14.0
> In the {{completeBlobUpload}} method in the DataStoreBlobStore class the returned blob
id is not being appended with the length suffix even if the property in on.
> This causes the references returned for these blob ids to be different than what are
returned from the BlobStore causing DSGC to treat the directly uploaded blob ids as candidates
for deletion. These would then be deleted when they have sufficiently aged, depending on the
configured {{blobMaxAgeInSecs}}. 
> This issue surfaces only with the DocumentNodeStore as SegmentNodeStore round trips the
id through {{Blob.getReference}} call which returns the length suffixed ids.

This message was sent by Atlassian JIRA

View raw message