[
https://issues.apache.org/jira/browse/OAK-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917841#comment-16917841
]
Alexander Klimetschek commented on OAK-8552:
--------------------------------------------
[~amitjain] I don’t think [~ianeboston] was suggesting to use the
jcr:lastModified JCR property for that. All of these could be internal fields
not exposed on the JCR level.
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. 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? (Just curious because I wasn’t aware of that)
Nonetheless, for the issue at hand I don’t think we need to change anything
stored in the NodeStore. The size/length is already stored in the NS as part of
the internal blob id.
> 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
> 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)
