[
https://issues.apache.org/jira/browse/OAK-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918283#comment-16918283
]
Amit Jain commented on OAK-8552:
--------------------------------
[~alexander.klimetschek]
Yes nothing needs to change now, I was just trying to highlight that there's
dynamism involved with lastModified while other properties are stable over the
lifetime of the blob even without de-deduplication.
{quote}With direct binary access we also no longer support de-duplication (too
costly), so that aspect can be ignored for binaries uploaded that way or if a
corresponding configuration is set
{quote}
But there's still a way that the binaries can be uploaded through JCR. So, we
would in an application still have the mix of both I guess.
{quote}But there is still copying/versioning of nodes which leads to multiple
references to the same blob - does this lead to a last modified update of the
blob?
{quote}
No copy of nodes would not update the timestamp of the blob.
Also, there's the case of a 'Shared' DataStore where nodes might have been
replicated from another instance through some form of replication and share the
DataStore.
> Minimize network calls required when creating a direct download URI
> -------------------------------------------------------------------
>
> Key: OAK-8552
> URL: https://issues.apache.org/jira/browse/OAK-8552
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: blob-cloud, blob-cloud-azure
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
> Fix For: 1.18.0
>
> Attachments: OAK-8552_ApiChange.patch
>
>
> We need to isolate and try to optimize network calls required to create a
> direct download URI.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
