Michael Ludwig-4 wrote:
MilkDud schrieb:
What do you expect the user to enter?
* dream theater innocence faded - certainly wrong
* dream theater innocence faded - much better
Most likely they would just enter dream theater innocence faded, no
quotes. Without any quotes around any
word. But
then I lose the ability to search for artist and track name together.
-Jason
Michael Ludwig-4 wrote:
MilkDud schrieb:
To be more specific, I'm indexing a collection of music albums that
have multiple tracks and an album artist. So, some searches will
contain both the artist name
separate documents at the track, artist, and album level) or having a field
that contains both the artist and track name concatenated, allowing for
phrase queries containing bother artist and track names.
Michael Ludwig-4 wrote:
MilkDud schrieb:
That part I understand and is what I have now
that this is an XY problem
Best
Erick
On Wed, Jun 17, 2009 at 4:52 PM, MilkDud jf...@limewire.com wrote:
Yea, not using stopwords at all. I do have tracks specified in the pf
param
along with a few other fields. That said, with a phrase query I lose the
ability to search for an artist
at
each track individually and if the artist + just one track match all the
search terms, then that counts as a match. Does that make sense? If i
index on the track level, that should work, but then i have to store
album/artist info on each track.
Michael Ludwig-4 wrote:
MilkDud schrieb
I'm trying to prevent a search from going across multiple values in a
multivalued field and am running into an issue. From what I've read, the
standard way to do this is with a positionIncrementGap that is larger than
the ps value. However, I can't make this a phrase query because there is
