[
https://issues.apache.org/jira/browse/LUCENE-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980565#action_12980565
]
Jason Rutherglen commented on LUCENE-2856:
------------------------------------------
bq. We could go with a -1 setting also - I see no reason to allocate an object,
and use auto-boxing as we do that
That's a style thing. I prefer null as it's conclusive and doesn't lead to
incorrect calculations, just NPEs.
bq. I think SegmentListener is not the proper name? I.e., it does not listen on
Segments, right? Maybe a SegmentMergeListener, or simple a MergeListener?
I had MergeListener, then changed it to be more generic. I think we should add
other segment events such as flush, open, clone, close, etc?
> Create IndexWriter event listener, specifically for merges
> ----------------------------------------------------------
>
> Key: LUCENE-2856
> URL: https://issues.apache.org/jira/browse/LUCENE-2856
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 4.0
> Reporter: Jason Rutherglen
> Attachments: LUCENE-2856.patch
>
>
> The issue will allow users to monitor merges occurring within IndexWriter
> using a callback notifier event listener. This can be used by external
> applications such as Solr to monitor large segment merges.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
