There isn't a difference in terms of perf or disk store, a type is actually
stored as another field in a doc. You will create multiple mappings in this
case for each zip, which is a waste in terms of storing the cluster state.
So, use a field and filter by it.
On Wed, Jun 13, 2012 at 6:50 PM, arta email@example.com wrote:
Thank you Ivan,
Good to know there isn't much difference.
Here'are my concerns:
- have the zip code as a type, so that we can search only for that zip
by specifying 'type'
- easy to construct query, as no explicit filter clause is necessary
- no need to have 'zip_code' field. so presumably saving disk space?
- type handling is a built-in feature of ES, so presumably faster
processing than query filter?
- I guess, default mapping is copied for each type when a type is added,
so more memory consumption?
- have the zip code as a field, then apply a filter by the field
Pros and cons opposite to 1)
In general, I'd like to know the difference in terms of, disk-usage,
memory-consumption and search-speed.
Thanks, again, for your help.
View this message in context:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.