You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2022/06/01 18:05:41 UTC
[GitHub] [druid] vtlim opened a new pull request, #12593: Update screenshots for Druid console doc
vtlim opened a new pull request, #12593:
URL: https://github.com/apache/druid/pull/12593
This PR updates screenshots in the Druid console doc and standardizes capitalization of "Druid console" in the docs.
This PR has:
- [x] been self-reviewed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r890517653
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The **Services** view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
+The view will attempt to infer your query and let you modify the query via contextual actions such as adding filters and changing the sort order when possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see the native query translation for a given Druid SQL query, and set the [query context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
-To send a native Druid query, you must start your query with `{` and format it as JSON.
+To send a native Druid query, start your query with `{` and format it as a JSON object.
Review Comment:
True. Rewording the previous sentence and removing the redundancy
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r890504243
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The **Home** view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The **Home** view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the **Home** view.
## Data loader
-The data loader view allows you to load data by building an ingestion spec with a step-by-step wizard.
+The data loader allows you to load data by building an ingestion spec with a step-by-step wizard.
Review Comment:
```suggestion
You can use the data loader to build an ingestion spec with a step-by-step wizard.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887212854
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The home view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The home view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the home view.
Review Comment:
```suggestion
You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the **Home** view.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r890517219
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The **Services** view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
+The view will attempt to infer your query and let you modify the query via contextual actions such as adding filters and changing the sort order when possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see the native query translation for a given Druid SQL query, and set the [query context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
Review Comment:
```suggestion
You can also use the query editor to issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] techdocsmith commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
techdocsmith commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r889421481
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The **Home** view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The **Home** view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the **Home** view.
## Data loader
-The data loader view allows you to load data by building an ingestion spec with a step-by-step wizard.
+The data loader allows you to load data by building an ingestion spec with a step-by-step wizard.
Review Comment:
```suggestion
You can use the data loader build an ingestion spec with a step-by-step wizard.
```
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The **Services** view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
+The view will attempt to infer your query and let you modify the query via contextual actions such as adding filters and changing the sort order when possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see the native query translation for a given Druid SQL query, and set the [query context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
-To send a native Druid query, you must start your query with `{` and format it as JSON.
+To send a native Druid query, start your query with `{` and format it as a JSON object.
Review Comment:
Don't all JSON objects begin with `{`?
##########
docs/operations/druid-console.md:
##########
@@ -22,17 +22,15 @@ title: "Web console"
~ under the License.
-->
-Druid includes a console for managing datasources, segments, tasks, data processes (Historicals and MiddleManagers), and coordinator dynamic configuration. You can also run SQL and native Druid queries in the console.
+Druid includes a web console for loading data, managing datasources and tasks, and viewing server status and segment information.
+You can also run SQL and native Druid queries in the console.
-The Druid Console is hosted by the [Router](../design/router.md) process.
-
-The following cluster settings must be enabled, as they are by default:
-
-- the Router's [management proxy](../design/router.md#enabling-the-management-proxy) must be enabled.
-- the Broker processes in the cluster must have [Druid SQL](../querying/sql.md) enabled.
-
-You can access the Druid console at:
+The following cluster settings must be enabled to use the Druid console. Note that these settings are enabled by default.
Review Comment:
```suggestion
Enable the following cluster settings o use the Druid console. Note that these settings are enabled by default.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887212452
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The home view provides a high-level overview of the cluster.
Review Comment:
```suggestion
The **Home** view provides a high-level overview of the cluster.
```
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The home view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The home view displays the following cards:
Review Comment:
```suggestion
The **Home** view displays the following cards:
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887194133
##########
docs/operations/druid-console.md:
##########
@@ -80,17 +92,20 @@ You can view and edit retention rules to determine the general availability of a
## Segments
-The segment view shows all the segments in the cluster.
+The segments view shows all the [segments](../design/segments.md) in the cluster.
Review Comment:
```suggestion
The **Segments** view shows all the [segments](../design/segments.md) in the cluster.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim merged pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim merged PR #12593:
URL: https://github.com/apache/druid/pull/12593
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887193757
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The home view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The home view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the home view.
## Data loader
-The data loader view allows you to load data by building an ingestion spec with a step-by-step wizard.
+The data loader allows you to load data by building an ingestion spec with a step-by-step wizard.
-After selecting the location of your data just follow the series for steps that will show you incremental previews of the data as it will be ingested.
-After filling in the required details on every step you can navigate to the next step by clicking the `Next` button.
+After selecting the location of your data, follow the series of steps displaying incremental previews of the data as it is ingested.
+After filling in the required details on every step you can navigate to the next step by clicking **Next**.
You can also freely navigate between the steps from the top navigation.
-Navigating with the top navigation will leave the underlying spec unmodified while clicking the `Next` button will attempt to fill in the subsequent steps with appropriate defaults.
+Navigating with the top navigation leaves the underlying spec unmodified while clicking **Next** attempts to fill in the subsequent steps with appropriate defaults.
## Datasources
-The datasources view shows all the currently enabled datasources.
-From this view, you can see the sizes and availability of the different datasources.
-You can edit the retention rules, configure automatic compaction, and drop data.
-Like any view that is powered by a DruidSQL query you can click `View SQL query for table` from the `...` menu to run the underlying SQL query directly.
+The datasources view shows all the datasources currently loaded on the cluster, as well as their sizes and availability.
+From the datasources view, you can edit the retention rules, configure automatic compaction, and drop data in a datasource.
Review Comment:
```suggestion
From the **Datasources** view, you can edit the retention rules, configure automatic compaction, and drop data in a datasource.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887195253
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The services view lets you see the current status of the nodes making up your cluster.
Review Comment:
```suggestion
The **Services** view lets you see the current status of the nodes making up your cluster.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r890502790
##########
docs/operations/druid-console.md:
##########
@@ -22,17 +22,15 @@ title: "Web console"
~ under the License.
-->
-Druid includes a console for managing datasources, segments, tasks, data processes (Historicals and MiddleManagers), and coordinator dynamic configuration. You can also run SQL and native Druid queries in the console.
+Druid includes a web console for loading data, managing datasources and tasks, and viewing server status and segment information.
+You can also run SQL and native Druid queries in the console.
-The Druid Console is hosted by the [Router](../design/router.md) process.
-
-The following cluster settings must be enabled, as they are by default:
-
-- the Router's [management proxy](../design/router.md#enabling-the-management-proxy) must be enabled.
-- the Broker processes in the cluster must have [Druid SQL](../querying/sql.md) enabled.
-
-You can access the Druid console at:
+The following cluster settings must be enabled to use the Druid console. Note that these settings are enabled by default.
Review Comment:
taking suggestion with fixed typo
```suggestion
Enable the following cluster settings to use the Druid console. Note that these settings are enabled by default.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887193516
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to. In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the Druid Console
+This topic presents the high-level features and functionality of the Druid console.
## Home
-The home view provides a high level overview of the cluster.
+The home view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The home view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups) from the top-level navigation of the home view.
## Data loader
-The data loader view allows you to load data by building an ingestion spec with a step-by-step wizard.
+The data loader allows you to load data by building an ingestion spec with a step-by-step wizard.
-After selecting the location of your data just follow the series for steps that will show you incremental previews of the data as it will be ingested.
-After filling in the required details on every step you can navigate to the next step by clicking the `Next` button.
+After selecting the location of your data, follow the series of steps displaying incremental previews of the data as it is ingested.
+After filling in the required details on every step you can navigate to the next step by clicking **Next**.
You can also freely navigate between the steps from the top navigation.
-Navigating with the top navigation will leave the underlying spec unmodified while clicking the `Next` button will attempt to fill in the subsequent steps with appropriate defaults.
+Navigating with the top navigation leaves the underlying spec unmodified while clicking **Next** attempts to fill in the subsequent steps with appropriate defaults.
## Datasources
-The datasources view shows all the currently enabled datasources.
-From this view, you can see the sizes and availability of the different datasources.
-You can edit the retention rules, configure automatic compaction, and drop data.
-Like any view that is powered by a DruidSQL query you can click `View SQL query for table` from the `...` menu to run the underlying SQL query directly.
+The datasources view shows all the datasources currently loaded on the cluster, as well as their sizes and availability.
Review Comment:
```suggestion
The **Datasources** view shows all the datasources currently loaded on the cluster, as well as their sizes and availability.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] vtlim commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
vtlim commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r890517817
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The **Services** view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
+The view will attempt to infer your query and let you modify the query via contextual actions such as adding filters and changing the sort order when possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see the native query translation for a given Druid SQL query, and set the [query context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
-To send a native Druid query, you must start your query with `{` and format it as JSON.
+To send a native Druid query, start your query with `{` and format it as a JSON object.
Review Comment:
```suggestion
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887196904
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The services view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The query view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
+The view will attempt to infer your query and let you modify the query via contextual actions such as adding filters and changing the sort order when possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see the native query translation for a given Druid SQL query, and set the [query context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query format](../querying/querying.md), which is JSON over HTTP.
-To send a native Druid query, you must start your query with `{` and format it as JSON.
+To send a native Druid query, start your query with `{` and format it as a JSON object.
## Lookups
-You can create and edit query time lookups via the lookup view.
+Access the lookups view from the **Lookups** card in the home view or by clicking on the gear icon in the upper right corner.
Review Comment:
```suggestion
Access the **Lookups** view from the **Lookups** card in the home view or by clicking on the gear icon in the upper right corner.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] ektravel commented on a diff in pull request #12593: Update screenshots for Druid console doc
Posted by GitBox <gi...@apache.org>.
ektravel commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r887196049
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your cluster.
+The services view lets you see the current status of the nodes making up your cluster.
You can group the nodes by type or by tier to get meaningful summary statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and display the results as a table.
-The view will attempt to infer your query and let you modify via contextual actions such as adding filters and changing the sort order when possible.
+The query view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
Review Comment:
```suggestion
The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and display the results as a table.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org