You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/01/28 10:53:39 UTC

[jira] [Assigned] (LUCENE-6999) Lucene60PointsWriter has a buggy close method

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

Michael McCandless reassigned LUCENE-6999:
------------------------------------------

    Assignee: Michael McCandless

> Lucene60PointsWriter has a buggy close method
> ---------------------------------------------
>
>                 Key: LUCENE-6999
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6999
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Michael McCandless
>         Attachments: LUCENE-6999_test.patch
>
>
> This will leak a file handle on e.g. disk full or other exceptions
> {noformat}
>   @Override
>   public void close() throws IOException {
>     if (closed == false) {
>       CodecUtil.writeFooter(dataOut); // something bad happens
>       dataOut.close();
> {noformat}
> I'm not a fan of these complex close methods, should we add a finish() to the codec api or similar?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org