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

Michael Garski updated LUCENENET-245:
-------------------------------------

    Attachment: LUCENENET-245.patch

Here's the patch, and it fixes issues in the following tests:

TestBooleanOr 
TestBooleanPrefixQuery 
TestBooleanScorer 
TestCustomSearcherSort 
TestDisjunctionMaxQuery 

Here's a summary of the changes:

DisjunctionMaxQuery : altered cloning to allow for equality check
FilteredQuery: removed unnecessary Clone method
MatchAllDocsQuery: removed unnecessary Clone method
MultiPhraseQuery: removed unnecessary Clone method
PhraseQuery: removed unnecessary Clone method
RangeQuery: removed unnecessary Clone method
TermQuery: removed unnecessary Clone method
TestMultiAnalyzer: removed unnecessary Clone method
JustCompileSearch: removed unnecessary Clone method
QueryUtils: removed unnecessary Clone method
TestBooleanPrefixQuery: removed Main & string ctor
TestBooleanScorer: removed string ctor
TestCustomSearcherSort: removed Main & string ctor; date issue (ms vs. ticks)
TestDisjunctionMaxQuery: nunit vs. junit argument ordering fix
 

> Query Fixes
> -----------
>
>                 Key: LUCENENET-245
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-245
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Michael Garski
>         Attachments: LUCENENET-245.patch
>
>
> I'm working on the tests regarding queries in Lucene.Net.Search.  I've 
> submitted one patch already (LUCENENET-234) and will hold off on submitting a 
> patch for this issue until that one has been reviewed & committed as I do not 
> want to submit duplicate fixes.
> This issue is primarily to let others know what I'm working on so there is no 
> duplication of effort.  I'll update this issue with progress and the tests 
> that are fixed as a result.

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

Reply via email to