apache.org
Subject: Re: Unexpected query rewrite from WordDelimiterFilterFactory and
SynonymFilterFactory
Thanks Jack! It's too bad I can't have catenate and generateParts both set
to "1" at query time. If I set catenate to "0", then I miss the case where
"wifi&
ex analyzer and do them only in the query analyzer - and multi-term
> synonyms don't work well, except for replacement synonyms at index time.
>
> See the "text_en_splitting" field type in the example schema.
>
> -- Jack Krupansky
>
> -Original Message- Fro
ple schema.
-- Jack Krupansky
-Original Message-
From: Chung Wu
Sent: Monday, May 14, 2012 7:01 PM
To: solr-user@lucene.apache.org
Subject: Unexpected query rewrite from WordDelimiterFilterFactory and
SynonymFilterFactory
Hi all!
I'm using Solr 3.6, and I'm seeing unex
: then in the CustomQueryParser I iterate over all the arguments adding
: each key/value to a Map. I then pass in this to the constructor of a
: basically copied ExtendedDismaxQParser (only difference is the added
: aliases and the logic to add those to the ExtendedSolrQParser).
:
: Now, the thi
Ok, so I think I have something working relatively well. I have a few
issues which I'm not sure how to address though. Currently when I
create my ParserPlugin in solrconfig I do the following
person_name^1.0 person_name_first^0.5 person_name_last^0.5
then in
I'm not following where the aliasing feature I'm looking for is.
Looking at the patch I didn't see it either. Essentially what I'm
looking for is when a user searches for person_name that the query
turns into person_name:john OR person_name_first:john OR
person_name_last:john. I don't see anythin
: Thanks Hoss. I'm not really sure where to begin looking with this, I
: quickly read the JIRA but don't see mention of exposing the multiple
: aliases. Can you provide any more details?
i refered to it as "uf" or "user fields" ... note the specific comment i
linked to in the first url, and th
Thanks Hoss. I'm not really sure where to begin looking with this, I
quickly read the JIRA but don't see mention of exposing the multiple
aliases. Can you provide any more details?
On Tue, Jul 12, 2011 at 1:19 PM, Chris Hostetter
wrote:
> : Taking a closer look at this it seems as if the
> : Di
: Taking a closer look at this it seems as if the
: DisjunctionMaxQueryParser supports doing multiple aliases and
: generating multiple queries, I didn't see this same capability in the
: ExtendedDismaxQParser, am I just missing it? If this capability were
it's never been exposed at a user level
arser. In its createParser method
>> (lucene 2.9.3 and solr 1.4) you can analyze the input query in the
>> param q and modify it accordingly.
>>
>> On 7/9/11, Jamie Johnson wrote:
>> > My organization is considering a few different approaches for indexing
>&
modify it accordingly.
>
> On 7/9/11, Jamie Johnson wrote:
> > My organization is considering a few different approaches for indexing
> > vs query rewrite and I'm trying to figure out what would be required
> > in order to implement some form of query rewrite. Lets say my
of the URL,
>> no need to write and compile and deploy code.
>>
>>> My organization is considering a few different approaches for indexing
>>> vs query rewrite and I'm trying to figure out what would be required
>>> in order to implement some form of query
use URL rewriting? Nginx has
> very powerful rewrite features and is capable of rewriting parts of the URL,
> no need to write and compile and deploy code.
>
>> My organization is considering a few different approaches for indexing
>> vs query rewrite and I'm trying to figu
If you use Solr over HTTP, then why don't you use URL rewriting? Nginx has
very powerful rewrite features and is capable of rewriting parts of the URL,
no need to write and compile and deploy code.
> My organization is considering a few different approaches for indexing
> vs query
ote:
>> you can try extending LuceneQParser. In its createParser method
>> (lucene 2.9.3 and solr 1.4) you can analyze the input query in the
>> param q and modify it accordingly.
>>
>> On 7/9/11, Jamie Johnson wrote:
>>> My organization is considering a few diff
cordingly.
>
> On 7/9/11, Jamie Johnson wrote:
>> My organization is considering a few different approaches for indexing
>> vs query rewrite and I'm trying to figure out what would be required
>> in order to implement some form of query rewrite. Lets say my index
&g
you can try extending LuceneQParser. In its createParser method
(lucene 2.9.3 and solr 1.4) you can analyze the input query in the
param q and modify it accordingly.
On 7/9/11, Jamie Johnson wrote:
> My organization is considering a few different approaches for indexing
> vs query rewri
My organization is considering a few different approaches for indexing
vs query rewrite and I'm trying to figure out what would be required
in order to implement some form of query rewrite. Lets say my index
has 2 fields first name and last name. When the user does a query
name:bob I'
: Think of the "name" field as less-important metadata field and "manu" as
: the more important and longer content field. When a person enters foo
: bar baz, I want to avoid matches in the manu/content field caused by
: matches of individual terms (that is why I removed manu field from the
: "
Hi,
I'm using DisMaxRequestHandler and trying to transform a user-entered
multi-term boolean query (e.g. foo bar baz).
I've configured DisMaxRH like so:
name^1.2 <-- I removed the manu field from here -->
manu^1.4
0 <-- try to requi
20 matches
Mail list logo
