Is there a way to configure the Field Collapse functionality to not collapse
Null fields? I want to collapse on a field that a certain percentage of
documents in my index have...but not all of them. If they don't have the
field I want it to be treated uncollapsed. Is there a setting to do this?
-
If I wanted to intercept a query and turn
q=romantic italian restaurant in seattle
into
q=romantic tag:restaurant city:seattle cuisine:italian
would I subclass QueryComponent, modify the query, and pass it to super? Or
is there a standard way already to do this?
What about changing it to
I wanted to extend my question some. My original question about collapsing
null fields is still open, but in trying to research elsewhere I see a lot
of angst about the Field Collapse functionality in general. Can anyone
summarize what the current state of affairs is with it? I'm on Solr 1.4,
ju
So QueryComponent is the place to do this? Are query analyzers already done?
Would I have access to stems, synonyms, tokens, etc of the query?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-modification-tp939584p940941.html
Sent from the Solr - User mailing list archiv
Someone else was recently asking a similar question (or maybe it was you but
worded differently :) ).
Putting user level security at a document level seems like a recipe for
pain. Solr/Lucene don't do frequent update well...and being highly optimized
for query, I don't blame them. Is there any wa
I haven't used this myself, but Solr supports a
http://wiki.apache.org/solr/UpdateXmlMessages#A.22rollback.22 rollback
function. It is supposed to rollback to the state at the previous commit. So
you may want to turn off auto-commit on the index you are updating if you
want to control what that
if you want only documents that have both values then make your q
q=content:videos+AND+content:songs
If you want the more open query, but to be able to tell which docs have
videos, which have songs and which have both...then I'm not sure. Using
debugQuery=on might help with your understanding,
Sounds like you want Payloads. I don't think you can guarantee a position,
but you can boost relative to others. You can give one author/book a boost
of 0 for the phrase Cooking, and another author/book a boost of .5 and yet
another a boost of 1.0. For searches that include the phrase Cooking, the
Gora,
Our environment, currently under development, is very nearly the exact same
thing as yours. My DB is currently only about 10GB, but likely to grow. We
also use Solr as primary repository (store all fields there), but use the DB
as a back up when Full Import is needed. Delta imports aren't th