From 9710369d52db3a96bc4d358bb4dbebadc3fae59f Mon Sep 17 00:00:00 2001 From: Rakshit Kumar <32777813+rakshitkumarcse@users.noreply.github.com> Date: Thu, 1 Nov 2018 02:02:25 +0530 Subject: [PATCH] Fixed grammatical errors. (#6246) * Fixed grammatical errors. * Update druid.rst --- docs/druid.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/druid.rst b/docs/druid.rst index b67354656..5d1499995 100644 --- a/docs/druid.rst +++ b/docs/druid.rst @@ -1,19 +1,19 @@ Druid ===== -Superset has a native connector to Druid, and a majority of Druid's +Superset has a native connector to Druid and a majority of Druid's features are accessible through Superset. .. note :: Druid now supports SQL and can be accessed through Superset's - SQLAlchemy connector. The long term vision is to deprecate + SQLAlchemy connector. The long-term vision is to deprecate the Druid native REST connector and query Druid exclusively through the SQL interface. Aggregations ------------ -Common aggregations, or Druid metrics can be defined and used in Superset. +Common aggregations or Druid metrics can be defined and used in Superset. The first and simpler use case is to use the checkbox matrix expose in your datasource's edit view (``Sources -> Druid Datasources -> [your datasource] -> Edit -> [tab] List Druid Column``). @@ -21,8 +21,8 @@ Clicking the ``GroupBy`` and ``Filterable`` checkboxes will make the column appear in the related dropdowns while in explore view. Checking ``Count Distinct``, ``Min``, ``Max`` or ``Sum`` will result in creating new metrics that will appear in the ``List Druid Metric`` tab upon saving the -datasource. By editing these metrics, you'll notice that they their ``json`` -element correspond to Druid aggregation definition. You can create your own +datasource. By editing these metrics, you'll notice that their ``json`` +element corresponds to Druid aggregation definition. You can create your own aggregations manually from the ``List Druid Metric`` tab following Druid documentation.