[
https://issues.apache.org/jira/browse/LUCENE-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400050#comment-16400050
]
Dawid Weiss commented on LUCENE-8205:
-------------------------------------
No magic maybe, but the complexity of interactions in indexing put me off a few
times I wanted to touch it. I'd be lovely for this part to be pluggable and
have gradually more complex implementations (like simple text in codecs)... :)
For example, I always lacked the "big picture" overview of how things in
indexing work (DWPT, deletes, generations with respect to commits, etc.). The
code is an ultimate resource, of course, but it'd be nice to have better docs
for this.
> 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
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-8205.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
