"date" fields currently require you to specify an underlying "field", because the assumption is that you're creating a synthetic field by parsing some other field. That's true when scanning and indexing, but not when querying or rolling up an index. You can work around this by specifying the field as itself (e.g., "timestamp[date;field=timestamp]"), but that's lame.
"date" fields currently require you to specify an underlying "field", because the assumption is that you're creating a synthetic field by parsing some other field. That's true when scanning and indexing, but not when querying or rolling up an index. You can work around this by specifying the field as itself (e.g., "timestamp[date;field=timestamp]"), but that's lame.