: I propose the following syntax similar to the DateMath syntax:
...
: Any date will be rounded to the nearest specified time and less significant
: units will be set to their least possible value.
: If it is not desirable to round to nearest element (many times users don't
: want a value greater than given value), we can have:
...
this starts to get into general territory of "a date math expression
applied to all input dates" ... so calling it "roundTo" may not be
appropriate.
it also starts to get ito the realm of "arbitrary processing of values
prior to storing/indexing ... which could be useful in other ways (ie:
parsing alternate date formats) and for other field types (ie: limit
numeric fiels to a certain range, round float input to an int, etc...)
which is something i've been hoping to work on for a while now ... let any
FieldType have an analyzer, and add/abuse a new <analyzer
type="preprocess"> for modifying the values before they are stored or
analyzed by the "index" analyzer.
-Hoss
