[LUCENE-3542] StandardQueryParser ignores AND operator for tokenized query terms

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4, 4.0-ALPHA
• Fix Version/s: 3.5, 4.0-ALPHA
• Component/s: modules/queryparser
• Lucene Fields: New, Patch Available
• Assignee: Simon Willnauer
• Reporter: Simon Willnauer
• Created: 29/Oct/11 20:36
• Updated: 28/Aug/22 13:00
• Resolved: 30/Oct/11 23:21

Description

The standard query parser uses the default query operator for query clauses that are created from tokenization in the query parser instead of the actual operator for the source term.

here is an example:

StandardQueryParser parser = new StandardQueryParser(new StandardAnalyzer(Version.LUCENE_34));
parser.setDefaultOperator(Operator.OR);
System.out.println(((BooleanQuery)parser.parse("_deleted:true AND title:東京", "f")));

this should yield:
+_deleted:true +(title:東 title:京)

as our former core query parser does but actually yields:
+_deleted:true title:東 title:京

seems like a bug to me, looking at the tests seems we don't test for this kind of queries in the standard query parser tests too.