[
https://issues.apache.org/jira/browse/OAK-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Hudea updated OAK-5874:
----------------------------
Description:
If a file is staged for async upload in UploadStagingCache and then another
call to AbstractSharedCachingDataStore.addRecord is made for a file with same
SHA1, the new call goes directly to the backed to write the file, because the
cache is not taking into account pending uploads. This makes 2 uploads to
happen for the same blob: one async (from UploadStagingCache) and one sync
(from AbstractSharedCachingDataStore.addRecord
(cc [~amitjain])
was:If a file is staged for async upload in UploadStagingCache and then
another call to AbstractSharedCachingDataStore.addRecord is made for a file
with same SHA1, the new call goes directly to the backed to write the file,
because the cache is not taking into account pending uploads. This makes 2
uploads to happen for the same blob: one async (from UploadStagingCache) and
one sync (from AbstractSharedCachingDataStore.addRecord
> Duplicate uploads might happen with AbstractSharedCachingDataStore
> ------------------------------------------------------------------
>
> Key: OAK-5874
> URL: https://issues.apache.org/jira/browse/OAK-5874
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Raul Hudea
> Assignee: Amit Jain
> Priority: Minor
> Attachments: OAK-5874.patch
>
>
> If a file is staged for async upload in UploadStagingCache and then another
> call to AbstractSharedCachingDataStore.addRecord is made for a file with same
> SHA1, the new call goes directly to the backed to write the file, because the
> cache is not taking into account pending uploads. This makes 2 uploads to
> happen for the same blob: one async (from UploadStagingCache) and one sync
> (from AbstractSharedCachingDataStore.addRecord
> (cc [~amitjain])
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
