lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "ComplexPhraseQueryParser" by iorixxx
Date Thu, 27 Mar 2014 23:52:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "ComplexPhraseQueryParser" page has been changed by iorixxx:
https://wiki.apache.org/solr/ComplexPhraseQueryParser?action=diff&rev1=2&rev2=3

Comment:
xml formatting added

  }}}
  
  
- After indexing example documents under example/exampledocs via 'java -jar post.jar *.xml'
utility
+ After indexing example documents under example/exampledocs via 'java -jar post.jar *.xml'
SimplePostTool utility.
  
  The query string 
  
@@ -32, +32 @@

  
  http://localhost:8983/solr/collection1/select?q=manu:%22a*%20c*%22&defType=complexphrase&fl=manu
  
- {{{
+ {{{#!highlight xml
  <doc>
    <str name="manu">Apple Computer Inc.</str>
  </doc>
@@ -45, +45 @@

  '''inOrder''' Parameter can be set in two ways.
  
  1) Its default value is true. If you want to set it to false in a permanent way : register
query parser with a different name in solrconfig.xml
- {{{
+ {{{#!highlight xml
   <!-- Un-ordered complex phrase query parser -->
   <queryParser name="unorderedcomplexphrase" class="org.apache.solr.search.ComplexPhraseQParserPlugin">
     <bool name="inOrder">false</bool>
@@ -92, +92 @@

  {{{
  q=features:"sto* up to 15*"&defType=complexphrase
  }}}
- does not return that document because [[http://lucene.apache.org/core/api/core/org/apache/lucene/search/spans/SpanNearQuery.html|SpanNearQuery]]
 has no good way to handle stopwords in a way analogous to [[http://lucene.apache.org/core/api/core/org/apache/lucene/search/PhraseQuery.html|PhraseQuery]]
. It is recommended not to use stopword elimination with this query parser.
+ does not return that document because [[http://lucene.apache.org/core/api/core/org/apache/lucene/search/spans/SpanNearQuery.html|SpanNearQuery]]
 has no good way to handle stopwords in a way analogous to [[http://lucene.apache.org/core/api/core/org/apache/lucene/search/PhraseQuery.html|PhraseQuery]].
It is recommended not to use stopword elimination with this query parser. 
+ If you really really have to remove stopwords, as a workaround, use a custom filter factory
that reduces given stopwords to some impossible token.
  

Mime
View raw message