Yes, I forgot that strings support alphanumeric ranges.
However, they will potentially be very memory intensive since you dont get the
trie-optimization and since strings take up more space than ints. Only way is
to try it out.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominve
adding
facet.query=timestamp:[20100601+TO+201006312359]&facet.query=timestamp:[20100701+TO+201007312359]...
in query should give the desired response without changing the schema or
re-indexing.
If you want to change the schema on the live index, make sure you do a
compatible change, as Solr does not do any type checking or schema change
validation.
I would ADD a field with another name for the tint field.
Unfortunately you have to re-index to have an index built on this field.
May I su
Thanks Mark. Yeah, storing it as 'tint' would be quite efficient.As i cannot
re-index the massive data, please let me know if the changes i make in
schema reflect to the already indexed data? I am not sure how type checking
happens in solr.
You can then do a facet query, specifying your desired r
If you're storing the timestamp as MMDDHHMM, why don't you make it
a trie-coded integer field (type 'tint') rather than text? That way,
I believe range queries would be more efficient. You can then do a
facet query, specifying your desired ranges as one facet query for
each range.
N
