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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2019/04/08 13:13:00 UTC

[jira] [Created] (OAK-8202) RemoteBlobProcessor should print a stack trace of the exceptions it swallows

Francesco Mari created OAK-8202:
-----------------------------------

             Summary: RemoteBlobProcessor should print a stack trace of the exceptions it swallows
                 Key: OAK-8202
                 URL: https://issues.apache.org/jira/browse/OAK-8202
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: segment-tar
            Reporter: Francesco Mari
            Assignee: Francesco Mari


In order to cope with the dryness of the {{BlobStore}} and {{DataStore}} API, {{RemoteBlobProcessor#shouldFetchBinary}} relies on exceptions to implement part of its logic. While this is a bad development practice, it was the only way to cope with in-memory binary IDs without spending excessive amounts of network and CPU. To Improve the transparency of the system, {{RemoteBlobProcessor}} should print a message at WARN level every time it swallows an exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)