I never really noticed until today that NumericField and NumericTokenStream don't support Short or Byte. (even though things like FieldCache do).
I'm wondering if there is a particular reason why they were *not* to included, or is it just that with numeric values in that small of a range, there isn't a lot of advantage to using multiple precision steps so it was never implemented?
It seems like there may be some valuable use cases where "Short" or "Byte" based NumericFields would be just as useful as an "Integer" and could save quite a bit of space if your index is really large (ie: numeric popularity field where values are always between 1-100, etc...)
-Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
