Don't allow sorting on geo_point
In discover, if you add a field of type geo_point to your search, and then try to sort on that field, the app errors out. It doesn't make sense to allow sorting on geo_point as this is not supported by ElasticSearch. Perhaps in the future we can allow sorting geo_point by distance from a given location.
syntax tweaks
add scriptable property to field aggs
Send date_histogram extended_bounds as a long. Closes #1868
fix code style for index patterns - use self
refactor the indexedArray code so it can be used for other fields
code style
saved_object should use self
Move validate_query and break out the parser and formatter
Fix validation of query strings containing only a number. Closes #1832
Coerce all non-strings & non-objects into strings
Tests for fromUser and toUser in query validator
move from camel case to snake case
Merge branch 'master' of github.com:elasticsearch/kibana into fix/extended-bounds-as-long
Add more tests
mapper should use self
courier should use self
remove unused (and broken) courer.getFieldsFor and reference to it
Prettify the display of the _source field in discover
remove patterncache, refactor fields

- make fetchFields 'private'
- use refreshFields to populate fields
- save after _fetchFields, not inside of it