Hi Daniel,
Solr has (e)dismax just for the propose you described.
https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser
Please see pf pf2 pf3 parameters
Ahmet
On Monday, June 27, 2016 3:55 PM, Daniel Bigham wrote:
Hi Ahmet,
Yes, thanks... that did come to mind a
No, it implies that Lucene is a low level library that allows people like
you and me, application developers, to develop applications that meet our
business and technical needs.
Like you, most of the things I work with prefer documents where the search
terms are close together, often preferably in
Hi Ahmet,
Yes, thanks... that did come to mind and is the strategy I'm playing with.
However, if you are giving a user a plain text field and using the Lucene query
parser, it doesn't create optional clauses for boosting purposes.
Does this imply that anyone wanting to use Lucene in conjunct
Hi Daniel,
You can add optional clauses to your query for boosting purposes.
for example,
temperate OR climates OR "temperate climates"~5^100
ahmet
On Friday, June 24, 2016 5:07 PM, Daniel Bigham wrote:
Something significant that I've noticed about using the default Lucene
query parser is
Something significant that I've noticed about using the default Lucene
query parser is that if your user enters a query like:
"temperate climates"
... it will get turned into an OR query:
temperate OR climates
This means that a document that contains the literal substring
"temperate climates
