MilkDud schrieb:
Michael Ludwig-4 wrote:
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 fields,
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 a
Hi Vicky,
Vicky_Dev schrieb:
We are also facing same problem mentioned in the post (we are using
dismaxrequesthandler)::
When we are searching for --q=prdTitle_s:"ladybird"&qt=dismax , we are
getting 2 results -- unique key ID =1000 and unique key ID =1001
(1) Append debugQuery=true to yo
Hi Michel,
We are also facing same problem mentioned in the post (we are using
dismaxrequesthandler)::
Ex: There is product title field in which --possible values
1) in unique key ID =1000
prdTitle_s field contains value "ladybird classic"
2) in unique key ID =1001
prdTitle_s field contains val
MilkDud schrieb:
Ok, so lets suppose i did index across just the album. Using that
index, how would I be able to handle searches of the form "artist name
track name".
What does the user interface look like? Do you have separate fields for
artists and tracks? Or just one field?
If i do the se
Ok, so lets suppose i did index across just the album. Using that index, how
would I be able to handle searches of the form "artist name track name". If
i do the search using a phrase query, this won't match anything because the
artist and track are not in one field (hence my idea of creating a
MilkDud schrieb:
Basically, what I am trying to do is index a collection of music for
an online music store. This contains information on the track, album,
and artist levels. These are all different object types in the same
schema and it does contain a lot of redundant information.
What's a
Sure. To be clear, I am actually revamping an existing index, that I've
found numerous problems with so far. Basically, what I am trying to do is
index a collection of music for an online music store. This contains
information on the track, album, and artist levels. These are all different
obj
H. Could you expand a bit more on the problem you're trying
to solve? The index organization you're hinting at seems close enough
to a set of database tables to make me wonder if you're using an
inappropriate index structure given the problem you want to solve.
Not that I know enough about you
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 and track combined. Two solutions i've
thought of include indexing at the track level only (right now i have
separ
MilkDud schrieb:
That part I understand and is what I have now. It's the fact that
since tracks is multivalued, and i search for a track "love me", i
will also get back artists that have the words love and me in separate
tracks.
Jason,
are you sure "me" isn't in a stopword list used to analy
Michael,
That part I understand and is what I have now. It's the fact that since
tracks is multivalued, and i search for a track "love me", i will also get
back artists that have the words love and me in separate tracks. Now with a
phrase query with a small ps and a large posIncGap that could w
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 and the track name. I can't make this a
single phrase query as it is indexed across two separate fields.
Use the
13 matches
Mail list logo
