Thank you very much, that seems to solve my issue.
However, I find this a little cumbersome. I need to filter the text
before any tokenizing takes place, so I have to implement a filtered
version of every analyzer I'm using (StandardAnalyzer and
SpanishAnalyzer and a custom analyzer right now)
Hi Jaime,
Please see o.a.l.analysis.custom.CustomAnalyzer.builder() to create custom
analyzers using a builder-style API.
Ahmet
On Friday, June 24, 2016 10:54 AM, Jaime wrote:
Thank you very much, that seems to solve my issue.
However, I find this a little cumbersome. I need to filter the te
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
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
