Field types for geohash to skip the analyzer

In a blog posthttp://engineering.foursquare.com/2012/08/09/foursquare-now-uses-elastic-search-and-on-a-related-note-slashem-also-works-with-elastic-search/,
foursquare engineering says "We got a non-trivial performance improvement
by switching the field types for our geohash to allow us to skip the
analyzer." Does anyone know specifically what they mean here? Are they
mapping their geohash as a string and setting 'index':'not_analyzed'?
Thanks in advance.

--

It does seem unnecessarily vague, but that's what it sounds like to me, too.

On Wednesday, November 28, 2012 7:29:45 AM UTC-8, Daniel Weitzenfeld wrote:

In a blog posthttp://engineering.foursquare.com/2012/08/09/foursquare-now-uses-elastic-search-and-on-a-related-note-slashem-also-works-with-elastic-search/,
foursquare engineering says "We got a non-trivial performance improvement
by switching the field types for our geohash to allow us to skip the
analyzer." Does anyone know specifically what they mean here? Are they
mapping their geohash as a string and setting 'index':'not_analyzed'?
Thanks in advance.

--