: +1, we should remove the Lucene doc values based queries.
Whoa...
Wouldn't that completley kill ~50% of the utility of having updatedable
DocValues support in Lucene?
Having an updatable field you can sort on is handy, but if the only way to
search/filter on the same effective (updated) value is to completley
re-index the entire document so you can get an (indexed) point value then
most of the use cases for updatable numeric values go out the window.
("Manager: can we do efficient realtime pricing updates?" - "Dev: well,
with updatable DocValues we can sort by the new prices, but searches will
still match the old price unless we completely reindex the doc." -
"Manager: What's the point of that?")
There is a *lot* of value in being able to do (slower) searching against
DocValues instead of an indexed numeric/points if you are willing to to
make the trade offs.
Hell, even w/o support for updatable DocValues (in Solr yet) i've seen
people make the concious choice to *stop* index their numeric fields and
only use DocValues because their biggest constraint was on disk index
size, and the speed of a DocValuesRangeQuery was "fast enough" for their
use cases as infrequently as they do them (since they needed/wanted
DocValues anyway for sorting)
-1 to removing doc values based queries, they fill a useful niche.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
