[
https://issues.apache.org/jira/browse/LUCENENET-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632604#action_12632604
]
Iliev Andrei commented on LUCENENET-151:
----------------------------------------
I don't like the approach to replace .Add by using Item property:
myCollection.Add(Key,myValue) -> myCollection[Key] = myValue. The reason:
java version of .Add adds an item only if the key does not already exists. But
myCollection[Key] = myValue will replace old value with a new one. Though it is
looked as not essential there are cases where it might be important. In such
a case it would be very hard to find the problem. So my point: .Net version
should be close to the java version (mimic java-object ) as much as possible. I
agree with Digi it would be better to write a new java compatible
Set/Hashtable interface.
A.I.
> Bug in
> Lucene.Net.Search.MultiPhraseQuery.ExtractTerms(System.Collections.Hashtable
> terms)
> ------------------------------------------------------------------------------------------
>
> Key: LUCENENET-151
> URL: https://issues.apache.org/jira/browse/LUCENENET-151
> Project: Lucene.Net
> Issue Type: Bug
> Environment: any/all
> Reporter: Doug Sale
> Priority: Minor
> Attachments: MultiPhraseQuery.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> when a query contains duplicate terms, attempting to add them to the
> Hashtable argument results in a thrown System.ArgumentException containing
> the message: "Item has already been added."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
