Thanks Robert, that helped.
On Thu, Feb 18, 2010 at 5:48 AM, Robert Muir wrote:
> i gave it a rough shot Lance, if there's a better way to explain it, please
> edit
>
> On Wed, Feb 17, 2010 at 10:23 PM, Lance Norskog wrote:
>
>> That would be great. After reading this and the PositionFilter clas
-user@lucene.apache.org
Sent: Thu, February 18, 2010 1:15:11 PM
Subject: Re: parsing strings into phrase queries
The PositionFilter worked great for my purpose along with another filter that I
build.
In my case, my indexed data may be something like "X150". So, a query for
"Nokia X150&
inst the "X150" part. So far I really like this for
partial part number searches. And then to boost exact matches, I used copyField
to create another field without PositionFilter. And then did an optional phrase
query on that.
From: Lance Norskog
To: solr-
i gave it a rough shot Lance, if there's a better way to explain it, please
edit
On Wed, Feb 17, 2010 at 10:23 PM, Lance Norskog wrote:
> That would be great. After reading this and the PositionFilter class I
> still don't know how to use it.
>
> On Wed, Feb 17, 2010 at 12:38 PM, Robert Muir wr
That would be great. After reading this and the PositionFilter class I
still don't know how to use it.
On Wed, Feb 17, 2010 at 12:38 PM, Robert Muir wrote:
> i think we can improve the docs/wiki to show this example use case, i
> noticed the wiki explanation for this filter gives a more complex s
i think we can improve the docs/wiki to show this example use case, i
noticed the wiki explanation for this filter gives a more complex shingles
example, which is interesting, but this seems to be a common problem and
maybe we should add this use case.
On Wed, Feb 17, 2010 at 1:54 PM, Chris Hostet
: take a look at PositionFilter
Right, there was another thread recently where almost the exact same issue
was discussed...
http://old.nabble.com/Re%3A-Tokenizer-question-p27120836.html
..except that i was ignorant of the existence of PositionFilter when i
wrote that message.
-Hoss
take a look at PositionFilter
On Feb 13, 2010 1:14 AM, "Kevin Osborn" wrote:
Right now if I have the query model:(Nokia BH-212V), the parser turns this
into +(model:nokia model:"bh 212 v"). The problem is that I might have a
model called Nokia BH-212, so this is completely missed. In my case, I
I don't see a good way to fix this without some heuristic you'd have to
implement to munge your query. There's no good for SOLR to intuit that
what you want is a partial match in this case. If you can create some
rules like "remove any single letters after numbers in the query"
that would be "good
Right now if I have the query model:(Nokia BH-212V), the parser turns this into
+(model:nokia model:"bh 212 v"). The problem is that I might have a model
called Nokia BH-212, so this is completely missed. In my case, I would like my
query to be +(model:nokia model:bh model:212 model:v).
This is
10 matches
Mail list logo
