lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From laimis <>
Subject [GitHub] lucenenet pull request: change how TopTermsRewrite instance of is ...
Date Wed, 22 Apr 2015 00:49:13 GMT
GitHub user laimis opened a pull request:

    change how TopTermsRewrite instance of is checked

    Changing the logic that checks if rewrite method is an instance of some sort of TopTermsRewrite
to match Lucene. Key change is here:
    Instead of checking for TopTermsRewrite<Q>, it seems like Lucene cares only if it
is TopTermsRewrite based class but does not care what parameter type is used and it does not
need to match SpanMultiTermQueryWrapper parameter type:
    At least that's how interpreted it. The tests seem to pass and this also fixes failing
test in TestSpanMultiTermQueryWrapper. TestFuzzy2

You can merge this pull request into a Git repository by running:

    $ git pull fuzzyquery_fix

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #130
commit d021a5228de4a35e82c96ad45266ec5a520d7e0f
Author: Laimonas Simutis <>
Date:   2015-04-22T00:43:04Z

    change how TopTermsRewrite instance of is checked


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message