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 hav
: 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
Hit the send button too fast ...
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.
Thanks,
Lajos
On 25/02/2014 22:58, Lajos wrote:
Guys,
I
Guys,
I've been testing out https://issues.apache.org/jira/browse/SOLR-5541 on
4.7RC4.
I previously had an elevate.xml that elevated 3 documents for a specific
query. My understanding is that I could, at runtime, exclude one of
those. So I tried that like this:
http://localhost:8080/solr/e
