You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Chris Male (JIRA)" <ji...@apache.org> on 2011/07/01 05:16:28 UTC
[jira] [Created] (LUCENE-3273) Convert Lucene Core tests over to a
simple MockQueryParser
Convert Lucene Core tests over to a simple MockQueryParser
----------------------------------------------------------
Key: LUCENE-3273
URL: https://issues.apache.org/jira/browse/LUCENE-3273
Project: Lucene - Java
Issue Type: Sub-task
Components: core/other
Reporter: Chris Male
Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Chris Male (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059642#comment-13059642 ]
Chris Male commented on LUCENE-3273:
------------------------------------
In defence of builders, its a great design pattern and I don't agree that its over-applied.
With all that said, I'll move away from them.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059531#comment-13059531 ]
Hoss Man commented on LUCENE-3273:
----------------------------------
I'm in favor of eliminating the QueryParser dependency, but i feel like this approach of adding things like "BooleanQueryBuilder" leads us down the road towards tests that are so verbose in query construction it will draw attention away from the important parts of the test -- doing something with those queres.
a while back when i wrote TestExplanations, i added a bunch of convenience methods for constructing esoteric queries that i couldn't get cleanly from the QueryParser (mainly spans) -- perhaps we should move towards generalizing that approach ... either in a Utility class where they can be staticly imported, or into LuceneTestCase? These days we could even use vargs for things like Phrase, Boolean, and SpanNear queries (we weren't using Java5 when i wrote the existing ones)
That way instead of things like this...
{code}
PhraseQuery q = new PhraseQuery(); // Query "this hi this is a test is"
q.add(new Term("field", "hi"), 1);
q.add(new Term("field", "test"), 5);
assertEquals("field:\"? hi ? ? ? test\"", q.toString());
{code}
...we could have ...
{code}
Query q = phraseQ("field", null, "hi", null, null, null, "test");
assertEquals("field:\"? hi ? ? ? test\"", q.toString());
{code}
And instead of this...
{code}
public void testDMQ8() throws Exception {
DisjunctionMaxQuery q = new DisjunctionMaxQuery(0.5f);
q.add(new BooleanQueryBuilder(FIELD)
.addTermQuery("yy")
.addQuery(QueryBuilderHelper.newTermQuery(FIELD, "w5", 100))
.get());
q.add(QueryBuilderHelper.newTermQuery(FIELD, "xx", 100000));
qtest(q, new int[] { 0,2,3 });
}
{code}
...we could have...
{code}
public void testDMQ8() throws Exception {
DisjunctionMaxQuery q = new DisjunctionMaxQuery(0.5f);
q.add(booleanQ(opt(termQ(FIELD, "yy")),
opt(termQ(FIELD, "w5", 100))));
q.add(termQ(FIELD, "xx", 100000));
qtest(q, new int[] { 0,2,3 });
}
{code}
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059538#comment-13059538 ]
Michael McCandless commented on LUCENE-3273:
--------------------------------------------
I would also prefer to keep tests very straightforward, even if that makes them more verbose. Ie just use the Lucene core API, and if the core API is insufficient we should improve it. I don't think we should be adding very much special test-only APIs.
In fact, why even add a builder here for BQ? Can't we just make the BQ and add the clauses?
In general I'm not a fan of builder APIs... I think they are over-applied these days (hammer!) and I don't think we need it here for our tests.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059579#comment-13059579 ]
Robert Muir commented on LUCENE-3273:
-------------------------------------
after reviewing the core tests, I think there is really not that many tests using the queryparser at all.
in fact it seems the only 'non-trivial' queries being built are inside the explanations tests (e.g. more than just a term, boolean, or phrase or whatever), if these are too laborious to make manually, maybe we can just have whatever is needed in the base TestExplanations... but I think it would be good to build queries directly in most places in general.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059533#comment-13059533 ]
Hoss Man commented on LUCENE-3273:
----------------------------------
to each his own i guess.
I just think it makes sense for utilities that do the banal stuff that's not central to the actually methods being tested should be as short as possible and get the hell out of the way -- the code you actually want to test should be verbose and catch your eye.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Michael McCandless (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059823#comment-13059823 ]
Michael McCandless commented on LUCENE-3273:
--------------------------------------------
Thanks Chris! Patch looks great.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3273) Convert Lucene Core tests over to a
simple MockQueryParser
Posted by "Chris Male (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Male updated LUCENE-3273:
-------------------------------
Attachment: LUCENE-3273.patch
Patch with first shot at this.
- MockQueryParser is introduced. It handles a very simple syntax consisting of boolean operators and can identify Wildcard queries. Cannot handle complex BooleanQuerys, boosts or PhraseQuerys.
- QueryBuilderHelper is introduced which provides some utilities methods for building queries (currently just to create a TermQuery with a boost)
- BooleanQueryBuilder and PhraseQueryBuilder are introduced to ease the process of programmatically creating complex BooleanQuerys and PhraseQuerys.
- All core Lucene tests (apart from those in the queryparser package) have been moved away from relying on QueryParser. In extremely trivial situations, TermQuerys are now directly instantiated. In others, the MockQueryParser is used. In complex scenarios, the Builder classes are used to programmatically create the queries.
- Some tests have been split up and moved around. Tests that did both parsing assertions and search assertions have been split so the parsing assertions go into TestQueryParser (since they are testing the QPs supported language).
Next step is to visit the contrib tests and clear those out too, so we can prevent any back dependencies on the queryparser module.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3273) Convert Lucene Core tests over to a
simple MockQueryParser
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3273:
--------------------------------
Attachment: LUCENE-3273_testboolean2.patch
here's my example, TestBoolean2.
in my opinion building the queries like this makes the test much more readable.
it adds 48 lines and deletes 29 lines of code...
I think adding these 19 lines of code to this 343 line test case is worth every penny, because its much easier to see what any given test does, e.g. just glance real quick at testQueries06 and you see its a BQ with one MUST and two MUST_NOTS, no parsing by the brain required.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059537#comment-13059537 ]
Robert Muir commented on LUCENE-3273:
-------------------------------------
the difference here, is that I think in general the tests should use/look like the API.
this makes them readable for people (e.g. new contributors) who already know lucene's API to
understand what the tests do.
For example in the lucene tests we added various randomization, but we tried to make it look just like the API, except deleting a space:
{noformat}
new IndexWriterConfig() -> newIndexWriterConfig()
new Directory() -> newDirectory()
new Field() -> newField()
...
{noformat}
in some of these tests, I think its actually *way more clear* to explicitly build the BQs and not use any builders or parsers, especially TestBoolean2 for example.
I fear sometimes, people get caught up on "more lines of code" == bad. I think this is wrong, sometimes more lines of code is good.
parsers, builder apis, and helper methods might reduce the number of lines of code, but they add additional layers and obfuscation that makes this a terrible tradeoff.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059576#comment-13059576 ]
Hoss Man commented on LUCENE-3273:
----------------------------------
bq. In general I'm not a fan of builder APIs... I think they are over-applied these days (hammer!)
bq. I think adding these 19 lines of code to this 343 line test case is worth every penny, because its much easier to see what any given test does, e.g. just glance real quick at testQueries06 and you see its a BQ with one MUST and two MUST_NOTS, no parsing by the brain required.
i don't disagree with either of you. particularly in this test where the whole point is testing BooleanQueries -- so lets actually have the test showing the construction of a BooleanQuery.
my point was more about tests where the construction of the Query object is ancillary to what the test is actually for.
that said: definitely in agreement that using the core api and constructing the queries right in the test leaves no room for ambiguity -- my main point was that if we're going to have "builders" to simplify the tests, let's make them short and terse like the QP syntax that use to be in those tests.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (LUCENE-3273) Convert Lucene Core tests over to
a simple MockQueryParser
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059532#comment-13059532 ]
Robert Muir commented on LUCENE-3273:
-------------------------------------
With all due respect hoss, i'd rather have the former than the latter.
The latter reminds me of solr tests which use this approach, I find them extremely painful to read.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (LUCENE-3273) Convert Lucene Core tests over to a
simple MockQueryParser
Posted by "Chris Male (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Male resolved LUCENE-3273.
--------------------------------
Resolution: Fixed
Fix Version/s: 4.0
Assignee: Chris Male
Committed revision 1143231.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Assignee: Chris Male
> Fix For: 4.0
>
> Attachments: LUCENE-3273.patch, LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (LUCENE-3273) Convert Lucene Core tests over to a
simple MockQueryParser
Posted by "Chris Male (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Male updated LUCENE-3273:
-------------------------------
Attachment: LUCENE-3273.patch
New patch, new ideas.
I've moved away from introducing anything new and have converted all the core tests over to instantiating Queries programmatically. No builders / helpers are used.
Everything compiles and passes again.
> Convert Lucene Core tests over to a simple MockQueryParser
> ----------------------------------------------------------
>
> Key: LUCENE-3273
> URL: https://issues.apache.org/jira/browse/LUCENE-3273
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: core/other
> Reporter: Chris Male
> Attachments: LUCENE-3273.patch, LUCENE-3273.patch, LUCENE-3273_testboolean2.patch
>
>
> Most tests use Lucene Core's QueryParser for convenience. We want to consolidate it into a QP module which we can't have as a dependency. We should add a simple MockQueryParser which does String.split() on the query string, analyzers the terms and builds a BooleanQuery if necessary. Any more complex Queries (such as phrases) should be done programmatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org