On 5/4/2015 6:29 AM, Steven White wrote:
> Thanks Doug. This is extremely helpful. It is much appreciated that you
> took the time to write it all.
>
> Do we have a Solr / Lucene wiki with such "did you know?" write ups? If
> not, just having this kind of knowledge in an email isn't good enough
Thanks Doug. This is extremely helpful. It is much appreciated that you
took the time to write it all.
Do we have a Solr / Lucene wiki with such "did you know?" write ups? If
not, just having this kind of knowledge in an email isn't good enough as it
won't be as searchable as a wiki.
Steve
On
Thank you.
-Original Message-
From: Doug Turnbull [mailto:dturnb...@opensourceconnections.com]
Sent: Thursday, April 30, 2015 11:33 AM
To: solr-user@lucene.apache.org; Dan Davis
Subject: Re: analyzer, indexAnalyzer and queryAnalyzer
- You write your own QParser plugins - can one keep
- You write your own QParser plugins - can one keep the features of edismax
for field boosting/phrase-match boosting by subclassing edismax? Assuming
yes...
hon-lucene-synonyms does this, but largely by copy pasting the code (sorry
about the broken link!)
pf2 and pf3 take the query "hello my na
Hi Doug, nice write-up and 2 questions:
- You write your own QParser plugins - can one keep the features of edismax
for field boosting/phrase-match boosting by subclassing edismax? Assuming
yes...
- What do pf2 and pf3 do in the edismax query parser?
hon-lucene-synonyms plugin links correction
Hi Doug,
Nice explanation of the query parsers. If you get a chance, can you please
take a quick look at the issue I am facing with multi term synonyms as
well?
http://lucene.472066.n3.nabble.com/Mutli-term-synonyms-tt4200960.html#none
is the problem I am facing. I am now able to perform multi ter
So Solr has the idea of a query parser. The query parser is a convenient
way of passing a search string to Solr and having Solr parse it into
underlying Lucene queries: You can see a list of query parsers here
http://wiki.apache.org/solr/QueryParser
What this means is that the query parser does wo
Hi Doug,
I don't understand what you mean by the following:
> For example, if a user searches for q=hot dogs&defType=edismax&qf=title
> body the *query parser* *not* the *analyzer* first turns the query into:
If I have indexAnalyzer and queryAnalyzer in a fieldType that are 100%
identical, the e
: 1) If the content of indexAnalyzer and queryAnalyzer are exactly the same,
: that's the same as if I have an analyzer only, right?
Effectively yes.
Subtle nuance: if you declare 1 analyzer, there is one Analyzer object in
ram. If you declare both, then there are 2 Analyzer objects in RAM -
*> 1) If the content of indexAnalyzer and queryAnalyzer are exactly the
same,that's the same as if I have an analyzer only, right?*
1) Yes
*> 2) Under the hood, all three are the same thing when it comes to what
kind*
*of data and configuration attributes can take, right?*
2) Yes. Both take in te
10 matches
Mail list logo
