[
https://issues.apache.org/jira/browse/LUCENE-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-6491:
---------------------------------
Attachment: LUCENE-6491.patch
Here is a patch that tries to avoid this issue for now:
- TermQuery refuses fake terms
- boolean rewrites fail if they encounter fake terms
- constant-score rewrite does not rewrite to a boolean query per segment if
any of the terms is a fake term
- moves auto-prefix tests for range and prefix queries to lucene/codecs
While testing this, I found a bug in BlockTermState which had isRealTerm
initially set to false so you could end up with real terms having a term state
with isRealTerm=false.
In the longer term we need to find a way for fake terms to not compare equal to
real terms...
> Failure in TestTermRangeQuery
> -----------------------------
>
> Key: LUCENE-6491
> URL: https://issues.apache.org/jira/browse/LUCENE-6491
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Alan Woodward
> Assignee: Michael McCandless
> Attachments: LUCENE-6491.patch
>
>
> ant test -Dtestcase=TestTermRangeQuery
> -Dtests.method=testAutoPrefixTermsKickIn -Dtests.seed=1970E47D58D0CF50
> -Dtests.locale=uk -Dtests.timezone=Canada/Newfoundland -Dtests.asserts=true
> -Dtests.file.encoding=US-ASCII
> Reproduces for me
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
