Is there any kind of general rule-of-thumb character limit in regards to 
faceting on very long strings?

I have a string field that I want to facet on (contains geographic data 
structured as a GeoJSON Feature), where the length is typically around 220 
characters. Is this too long to facet on, performance-wise?

If this (~220 chars) is too long, is there some way to hash the long string and 
copyField for better performance, but in a way that the original string values 
can be returned as facets in the response?

I know this question is a bit vague, and I would imagine mileage will vary 
depending on the specifics of the situation. I anticipate the entire index to 
include about 2 million documents, with possibly about 200,000 unique values 
for this GeoJSON string field.

Thanks!

Eben English

Reply via email to