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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/01/14 18:40:40 UTC
[jira] [Resolved] (OAK-3872) [RDB] Updated blob still deleted even
if deletion interval lower
[ https://issues.apache.org/jira/browse/OAK-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved OAK-3872.
---------------------------------
Resolution: Fixed
trunk: http://svn.apache.org/r1724423
1.2: http://svn.apache.org/r1724632
1.0: http://svn.apache.org/r1724659
(the backport to 1.0 was a bit painful because of other changes not being backported; sigh)
> [RDB] Updated blob still deleted even if deletion interval lower
> ----------------------------------------------------------------
>
> Key: OAK-3872
> URL: https://issues.apache.org/jira/browse/OAK-3872
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob, rdbmk
> Affects Versions: 1.2.9, 1.0.25, 1.3.13
> Reporter: Amit Jain
> Assignee: Julian Reschke
> Fix For: 1.0.26, 1.2.10, 1.3.14
>
> Attachments: OAK_3872.patch
>
>
> If an existing blob is uploaded again, the timestamp of the existing entry is updated in the meta table. Subsequently if a call to delete (RDBBlobStore#countDeleteChunks) is made with {{maxLastModifiedTime}} parameter of less than the updated time above, the entry in the meta table is not touched but the data table entry is wiped out.
> Refer https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document/rdb/RDBBlobStore.java#L510
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)