Preserve objects in arrays when flattening search response
Disable discover buttons
If a row contains arrays of objects, we don't want to enable the discover search buttons.
[tableVis] allow displaying partial rows, fixes #1911
Metric Vis
Create the metric visualization, which is a simple visualization that shows in large text the calculation of a metric.

Closes #1666.
Fix index pattern search error
Closes issue #1899.

When using the index name search, if you type quickly, then the search is not invoked after you have finished typing. This is because we had specified options to lodash debounce (https://lodash.com/docs#debounce) to execute the search function on the leading edge of the specified timeout, instead of the trailing edge (which it does by default). This change removes the overrides and fixes the issue.
remove console logging
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.
[vis] use the isHierarchical method, not the property of the visType
[tableVis] allow configuring the way metrics are calculated for the metric vis
[aggResponse/tabify] allow overriding partialRows for hierarchical vis types
[aggResponse/tabify] tests to support 227d6fa
[tableVis] tests!
Make changes as per Spencer's suggestions
[visaulize] [dash] handle titles like discover
[kibana] expose the current app on $rootScope
[docTitle] new docTitle service
[dashboard] use the new docTitle service
[aggConfig] allow mutliple metrics to be written in the DSL
[aggConfig] added test to prove 1ae3713
[tabify] write metrics for partial & hierarchical rows