e index, at
multiple levels of granularity. Some of this conversation is captured
on the Wiki at:
http://wiki.apache.org/jakarta-lucene/FlexibleIndexing
Maybe you could modify the above page to include your requirements?
Steve
Furash Gary wrote:
> I'm sure this is just a design point that
The behavior I want is that if I store a name (Gary Furash), a user who
searches for "Gary Furash" gets a strong hit, wheras a user who seaches
for "Gray Furish" gets a moderate hit. I currently achieve this by
1. using a custom analyzer on insertion/search that tokenizes a
"soundex" version of t
I'm sure this is just a design point that I'm missing, but is there a
way to have my document objects know more about themselves?
At the time I create my document, I know a bit about how information is
being stored in it (e.g., this field represents a SOUNDEX copy, etc.),
yet the logic for that ki
I have a couple of fields like this (e.g., a given case can have 1:many
case numbers and 1:many defendant aliases). So there's no problem with
adding the same field n times to a given document? If so, that's
perfect and i'll add it to the faq. I was concatenating before and
getting false matche
Thanks. It sounds like putting tokens in the same spot for names makes
sense, so I end up with:
GaryFurash
[Soundex Gary] [Soundex Furash]
is the way to go. I had seen a quote that mention positioning at the
same spot but it didn't make any sense at t
In my defense I assumed it would be more obscurely named ;-)
G
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Disk is cheap, and I can always put the field elsewhere if I need to
sort on it, but user response time ... Priceless. I'll give #1 a shot.
I'm going to try encoding them in the same position, see what happens.
Thanks!
-
To unsu
For some things, it's obvious that you would have to put them both on
the front end (during indexing) and on the back end. E.g., if you want
to do a soundex search, you'd want to encode the words with their
soundex version during index creation, and when you query incode the
user's search input as
I'm guessing they're neither the guy from Cheers nor the sociology term
;-)
The examples have you creating them before you do searches. What are
they? The javadoc doesn't really explain their function (or at least
not in a way I could figure out). Thanks.
G
---
Maybe I'm approaching this wrong (apologies) and didn't search correctly
through the archives (mia culpa), but...
If I want to apply a different analyzer to different fields in the
document, how do I do that? It seems like when you create the index you
pass it an analyzer, and that's the one you'
am, but I'm
not sure what.
2. I've got a bunch of names assocated with a single person (aliases)
(document): e.g., "Gary Furash", "Gary 'The Nose' Furash", "Gary
Furnham". If I stick them all in the same field ("names"), and search
on &quo
11 matches
Mail list logo
