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 2024/01/24 12:48:00 UTC

[jira] [Commented] (OAK-10573) Make distinction for azure timeout settings between write and read operations

    [ https://issues.apache.org/jira/browse/OAK-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810365#comment-17810365 ] 

Julian Reschke commented on OAK-10573:
--------------------------------------

[~miroslav] - is this resolved with https://github.com/apache/jackrabbit-oak/commit/e2da4d7f84fcf2c4a6e729fe073529e87f6062f7 ?


> Make distinction for azure timeout settings between write and read operations
> -----------------------------------------------------------------------------
>
>                 Key: OAK-10573
>                 URL: https://issues.apache.org/jira/browse/OAK-10573
>             Project: Jackrabbit Oak
>          Issue Type: Story
>          Components: segment-azure
>    Affects Versions: 1.58.0
>            Reporter: Miroslav Smiljanic
>            Assignee: Miroslav Smiljanic
>            Priority: Major
>
> Currently, the Azure blob sore client has operation timeout configuration options exposed via system properties. There is not distinction between configuration for write and read operations. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)