[
https://issues.apache.org/jira/browse/SOLR-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119732#comment-15119732
]
Christine Poerschke commented on SOLR-839:
------------------------------------------
bq. why does fieldName appear on BooleanQuery? Can one specify the fieldName on
<TermQuery> instead (or in addition to)?
As i understand it the fieldname on the BooleanQuery will only get used if the
Term(s)Query does not specify its own fieldName. TermQuery certainly can
specify its own fieldname, we usually use TermQuery like that.
{{lucene/queryparser/src/test/org/apache/lucene/queryparser/xml}} has various
test *.xml files, not sure if/where there's more formal documentation re: the
various queries that are supported and what their xml elements and attributes
are.
> XML Query Parser support (deftype=xmlparser)
> --------------------------------------------
>
> Key: SOLR-839
> URL: https://issues.apache.org/jira/browse/SOLR-839
> Project: Solr
> Issue Type: New Feature
> Components: query parsers
> Affects Versions: 1.3, 5.4, Trunk
> Reporter: Erik Hatcher
> Assignee: Christine Poerschke
> Priority: Minor
> Fix For: 5.5, Trunk
>
> Attachments: SOLR-839-object-parser.patch, SOLR-839.patch,
> SOLR-839.patch, SOLR-839.patch, lucene-xml-query-parser-2.4-dev.jar
>
>
> Lucene includes a query parser that is able to create the full-spectrum of
> Lucene queries, using an XML data structure.
> This patch adds "xml" query parser support to Solr.
> Example (from
> {{lucene/queryparser/src/test/org/apache/lucene/queryparser/xml/NestedBooleanQuery.xml}}):
> {code}
> <BooleanQuery fieldName="contents">
> <Clause occurs="should">
> <BooleanQuery fieldName="contents">
> <Clause occurs="must">
>
> <TermQuery>doesNotExistButShouldBeOKBecauseOtherClauseExists</TermQuery>
> </Clause>
> </BooleanQuery>
> </Clause>
> <Clause occurs="should">
> <TermQuery>bank</TermQuery>
> </Clause>
> </BooleanQuery>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
