lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Sale (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LUCENENET-133) bug in IndexWriter.RegisterMerge()
Date Thu, 17 Jul 2008 15:13:31 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Doug Sale resolved LUCENENET-133.
---------------------------------

    Resolution: Fixed

The fix for this bug is to simply not add the SegmentInfo to the mergeSegments Hashtable if
it is already present in the Hashtable.

This was caused by a faulty conversion:
- in Java, adding a duplicate to a Set replaces the entry
- in C#, an ArgumentException is thrown

This fix corrects the following test cases:

Lucene.Net.Index.TestAddIndexesNoOptimize.TestNoMergeAfterCopy
Lucene.Net.Index.TestAddIndexesNoOptimize.TestMergeAfterCopy

Lucene.Net.Index.TestIndexWriter.TestTermVectorCorruption


> bug in IndexWriter.RegisterMerge()
> ----------------------------------
>
>                 Key: LUCENENET-133
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-133
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Doug Sale
>         Attachments: IndexWriter.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> When adding a duplicate segment to the Hastable 'mergingSegments', C# Hastable implementaion
throws an ArgumentException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message