Thanks Hoss, that makes sense.
Anyway, I like the new paradigm better ... it allows for more
intelligent elevation control.
Cheers,
L
On 25/02/2014 23:26, Chris Hostetter wrote:
: What is seems that is happening is that excludeIds or elevateIds ignores
: what's in elevate.xml. I would have expected (hoped) that it would layer on
: top of that, which makes a bit more sense I think.
That's not how it's implemented -- i believe Joel implemented this way
intentional because otherwise if the elevate.xml said "elevate A,B and
exclude X,Y" there would be no simple way to say "instead of what's in
elevate.xml, i want to elevate X,Y and i don't wnat to exclude *anything*"
I made sure this was explicitly documented in the ref guide...
https://cwiki.apache.org/confluence/display/solr/The+Query+Elevation+Component#TheQueryElevationComponent-TheelevateIdsandexcludeIdsParameters
"If either one of these parameters is specified at request time, the the
entire elevation configuration for the query is ignored."
-Hoss
http://www.lucidworks.com/