You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Simon Willnauer (JIRA)" <ji...@apache.org> on 2018/03/14 15:57:00 UTC

[jira] [Created] (LUCENE-8205) Simplify AbortingException handling and tragic event logic

Simon Willnauer created LUCENE-8205:
---------------------------------------

             Summary: Simplify AbortingException handling and tragic event logic
                 Key: LUCENE-8205
                 URL: https://issues.apache.org/jira/browse/LUCENE-8205
             Project: Lucene - Core
          Issue Type: Improvement
    Affects Versions: 7.4, master (8.0)
            Reporter: Simon Willnauer
            Assignee: Simon Willnauer
             Fix For: 7.4, master (8.0)


Today we try to signal via exception handling if an exception is aborting
 and/or a tragic event. This causes today that we ignore certain exception if we
are in the process of handling a such which is generally bad practice. This
change simplify the signaling of aborting exceptions and separates acting on
tragic events and closing the writer because of a tragic event. This in-turn
simplifies lock ordering since we never acquire a lock anymore inside the
tragic event code.




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

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