what I need. I very clearly know my fields and values and that should
give me enormous leverage when querying if I could build a query to do that
Christian
--
Christian Bongiorno
index
> OR index them in the same index but simply store
> the data (don't index it) and the HST documents won't
> interfere with your searches on "similar items".
>
> Mostly, this is just trying to see if I understand what
> you're trying to accompli
fields
> > and searching that concatenated field with and/or (except that MFQ does
> > interesting things with boosting).
> >
> > But if you know exactly what terms you require in which field, the
> > standard query parser is fine. i.e. +material:leather +gender:fem
boostNumber);
}
booleanQuery.add(termQuery, BooleanClause.Occur.SHOULD);
}
}
LOG.warn("Boolean query: " + booleanQuery.toString());
return booleanQuery;
}
return null;
}
--
Christian Bongiorno
turns out the index is being built with lower-case terms which is why we
aren't getting hits the way we expect. When I change my search terms to
lower I see more of what I expect.
Gonna keep working on this and post updates.
On Wed, Aug 12, 2009 at 12:46 PM, Christian Bongiorno <
