Hello,
Giving the code
https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/schema/TrieField.java#L727
it creates NumericDocValuesField only.
try to define field as multivalued, giving the code it creates
SortedSetDocValuesField.
On Wed, Aug 19, 2015 at 11:13 PM,
I see. The UninvertingReader even throws an IllegalStateException if you try
read a numeric field as a sorted doc values. I may have to index extra
fields to support my document collapsing scheme. Thanks for responding.
--
View this message in context:
I'm trying to upgrade my custom post filter from Solr 4.9 to 5.2. This filter
collapses documents based on a user chosen field set. The key to the whole
thing is determining document uniqueness based on a fixed int array of field
value ordinals. In 4.9 this worked regardless of the field type. In
One error (others perhaps?) in my statement ... the code
searcher.getLeafReader().getSortedDocValues(field)
just returns null for numeric and date fields. That is why they appear to be
ignored, not that the ordinals are all absent or equivalent. But my question
is still valid I think!
--
View
tedsolr tsm...@sciquest.com wrote:
I'm sure there is a good reason why SortedDocValues exposes
the backing dictionary and [Sorted]NumericDocValues does not.
There is: Numerics does not have a backing dictionary. Instead of storing the
values via the intermediate ordinals-map (aka by
