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 2019/09/30 07:36:04 UTC

[jira] [Closed] (OAK-8600) [Direct Binary Access] Log exceptions at debug level for expected exceptions

     [ https://issues.apache.org/jira/browse/OAK-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke closed OAK-8600.
-------------------------------

> [Direct Binary Access] Log exceptions at debug level for expected exceptions
> ----------------------------------------------------------------------------
>
>                 Key: OAK-8600
>                 URL: https://issues.apache.org/jira/browse/OAK-8600
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob-cloud, blob-cloud-azure
>            Reporter: Matt Ryan
>            Assignee: Matt Ryan
>            Priority: Major
>             Fix For: 1.18.0
>
>
> Recent data store optimizations to reduce network API calls means a greater reliance on exception handling to minimize the number of calls, and catching thrown exceptions from these API calls (for example, calling a network API and handling a thrown exception for a missing blob instead of checking for blob existence first, then calling the other network API).
> We need to change any logging of these issues to debug level, and/or change the log messages to avoid looking like there are problems or uncaught exceptions in the logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)