Re: Searching across multivalued fields

2009-06-18 Thread MilkDud
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 innoc

Re: Searching across multivalued fields

2009-06-17 Thread MilkDud
ally, i'd like it to look 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

Re: Searching across multivalued fields

2009-06-17 Thread MilkDud
a valid > opinion, but there's at least a chance that this is an XY problem > > Best > Erick > > On Wed, Jun 17, 2009 at 4:52 PM, MilkDud wrote: > >> >> Yea, not using stopwords at all. I do have tracks specified in the pf >> param >> along with

Re: Searching across multivalued fields

2009-06-17 Thread MilkDud
have 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

Re: Searching across multivalued fields

2009-06-17 Thread MilkDud
cGap that could 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. S

Searching across multivalued fields

2009-06-16 Thread MilkDud
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 anoth