During data import can you update a record with min and max fields, these
would be equal in the case of a single non range value.
I know this is not a solr solution but a data pre-processing one but would
work?
Failing the above i've saw in the docs reference to a compound value field
(in the con
I'm not sure you're right that it will result in an out-of-memory error
if the range is too large. I don't think it will, I think it'll be fine
as far as memory goes, because of how Lucene works. Or do you actually
have reason to believe it was causing you memory issues? Or do you just
mean me
Hi!
I have a typical case where in an attribute (in a DB record) can
contain different ranges of numeric values. Let us say the range
values in this attribute for "record1" are
(2-4,5000-8000,45000-5,454,231,1000). As you can see this
attribute can also contain isolated numeric values
