[
https://issues.apache.org/jira/browse/LUCENE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550934
]
Michael McCandless commented on LUCENE-1088:
--------------------------------------------
OK, though, now I'm wondering whether one should simply subclass PriorityQueue
to achieve this change to insert()'s behavior, instead of adding these two
methods. Is there a reason why this approach can't be used instead?
I realize this would replicate the logic in insert() in a subclass, but I think
that's a fairly minor cost vs increasing the complexity of PriorityQueue by
adding these two methods?
> PriorityQueue 'wouldBeInserted' method
> --------------------------------------
>
> Key: LUCENE-1088
> URL: https://issues.apache.org/jira/browse/LUCENE-1088
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Other
> Reporter: Peter Keegan
> Assignee: Michael McCandless
> Attachments: LUCENE-1088.patch
>
>
> This is a request for a new method in PriorityQueue
> public boolean wouldBeInserted(Object element)
> // returns true if doc would be inserted, without inserting
> This would allow an application to prevent duplicate entries from being added
> to the queue.
> Here is a reference to the discussion behind this request:
> http://www.nabble.com/FieldSortedHitQueue-enhancement-to9733550.html#a9733550
--
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]
