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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/12/15 10:08:46 UTC

[jira] [Resolved] (OAK-3703) Improve handling of IOException

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

Michael Dürig resolved OAK-3703.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.3.13

Fixed at http://svn.apache.org/viewvc?rev=1720095&view=rev


> Improve handling of IOException
> -------------------------------
>
>                 Key: OAK-3703
>                 URL: https://issues.apache.org/jira/browse/OAK-3703
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: resilience, technical_debt
>             Fix For: 1.3.13
>
>
> {{SegmentStore.writeSegment}} doesn't specify its behaviour in the face of IO errors. Moreover {{FileStore.writeSegment}} just catches any {{IOException}} and throws a {{RuntimeException}} with the former as its cause. 
> I think we need to clarify this as an immediate cause of the current state is that some of the {{SegmentWriter}} write methods *do* throw an {{IOException}} and some *don't*. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)