[
https://issues.apache.org/jira/browse/OAK-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916035#comment-16916035
]
Matt Ryan commented on OAK-8552:
--------------------------------
WRT removing the existence check from {{createHttpDownloadURI()}}, I see the
following options:
# Leave the code as-is and live with the O(100ms) cost of checking existence
before creating the signed URI - but clients know the blob existed at the time
the URI was created
# Revert OAK-7998, dropping the cost of generating a signed URI to O(100
microseconds) but clients may get a URI that returns a 404 (blob not yet in
storage)
# Leave the fix for OAK-7998 but add some form of cache or lookup table, which
would consume additional memory but could speed up a non-zero number of signed
URI generation requests, while still guaranteeing to clients that the blob
existed at the time the URI was created
** If doing this we would need to figure out how to populate the cache or
lookup table - on demand, at startup, etc.
I'm pretty sure [~ianeboston] would vote for #2 or #3. Any other options or
votes?
> 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)
