The main query for a solr search is specified via the q
parameter. Example of standard query is shown below:
http://localhost:8983/solr/query?q=test
If you add debug=query, you can see see how Solr is parsing your query. You can do as shown below:
http://localhost:8983/solr/query?debug=query&q=hello
Example of solr query is shown below:
{
"responseHeader"
:{
"status"
:0,
"QTime"
:0,
"params"
:{
"q"
:
"hello"
,
"debug"
:
"query"
}},
"response"
:{
"numFound"
:0,
"start"
:0,
"docs"
:[]
},
"debug"
:{
"rawquerystring"
:
"hello"
,
"querystring"
:
"hello"
,
"parsedquery"
:
"text:hello"
,
"parsedquery_toString"
:
"text:hello"
,
"QParser"
:
"LuceneQParser"
}}
response
section will normally contain the top ranking documents for the query. In the above example, no document matched query.text
was used as the default field to search.hello'
is the word we are going to match.text:”john smith”
Yonik Seeley
but will not match smith v john
or smith john .This query will match text containing solr analytics, solr faceted analytics (edit distance 1), and analytics solr (edit distance 1). It will not match solr super faceted analytics or analytics faceted solr since those would both require an edit distance of 2 to get the terms into the matching positions.
A boolean query contains multiple clauses. A clause may be optional, mandatory, or prohibited.solr search
The default operator is “OR”, meaning that clauses are optional. When there are no mandatory clauses, at least one of the optional clauses in a query must match for the full query to match. The example query above will thus match documents containing solr or search (or both) in the default search field.
Boolean query examples:
+solr +search facet -highlight /* uses + for mandatory and – for prohibited */
solr AND search OR facet NOT highlight /* this is equivalent to the first query */
Semantics: solr and search must both match, highlight must not match. facet may or may not match but will contribute to the query score if it does (i.e. the presence of the facet only affects scores of matching documents, not which documents match.)
text:solr^10 text:rocks
(inStock:true AND text:solr)^123.45 text:hi
A range query selects documents with values between a specified lower and upper bound. Range queries work on numeric fields, date fields, and even string and text fields.Range Query Examples:
age:[18 TO 30] // matches age 18-30 inclusive (endpoints 18 and 30 are included)
age:[65 TO *] // “open ended” range matches age>65
A ConstantScoreQuery is like a boosted query, but it produces the same score for every document that matches the query. The score produced is equal to the query boost. The ^= operator is used to turn any query clause into a ConstantScoreQuery.Constant Score Query Examples:
+color:blue^=1 text:shoes
(inStock:true text:solr)^=100 native code faceting
A filter query retrieves a set of documents matching a query from the filter cache. Since scores are not cached, all documents that match the filter produce the same score (0 by default). Cached filters will be extremely fast when they are used again in another query.Filter Query Example:
description:HDTV OR filter(+promotion:tv +promotion_date:[NOW/DAY-7DAYS TO NOW/DAY+1DAY])
One can embed comments in a query using C-style comments surrounded with /* */. Comments can be nested.Query Comments Example:
description:HDTV /* TODO: +promotion:tv +promotion_date:[NOW/DAY-7DAYS TO NOW/DAY+1DAY] */