ektravel commented on code in PR #16842:
URL: https://github.com/apache/druid/pull/16842#discussion_r1704753565


##########
docs/tutorials/tutorial-query-deep-storage.md:
##########
@@ -25,7 +25,7 @@ sidebar_label: "Query from deep storage"
 
 Query from deep storage allows you to query segments that are stored only in 
deep storage, which provides lower costs than if you were to load everything 
onto Historical processes. The tradeoff is that queries from deep storage may 
take longer to complete. 
 
-This tutorial walks you through loading example data, configuring load rules 
so that not all the segments get loaded onto Historical processes, and querying 
data from deep storage.
+This tutorial walks you through loading example data, configuring load rules 
so that not all the segments get loaded onto Historical processes, and querying 
data from deep storage. If you have [centralized datasource schema 
enabled](../configuration/index.md#centralized-datasource-schema), you can 
query datasources that are only in deep storage and don't need to make sure at 
least one segment is available on a Historical.

Review Comment:
   ```suggestion
   This tutorial walks you through loading example data, configuring load rules 
so that not all the segments get loaded onto Historical services, and querying 
data from deep storage. If you have [centralized datasource schema 
enabled](../configuration/index.md#centralized-datasource-schema), you can 
query datasources that are only in deep storage and don't need to make sure at 
least one segment is available on a Historical.
   ```



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to