This is an automated email from the ASF dual-hosted git repository.
karan pushed a commit to branch 28.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/28.0.0 by this push:
new 7f33ebc33b9 docs: remove experimental note from query from deep
storage docs (#15132) (#15157)
7f33ebc33b9 is described below
commit 7f33ebc33b98fcb09e53d292649dd237adcd01df
Author: Laksh Singla <[email protected]>
AuthorDate: Mon Oct 16 10:41:20 2023 +0530
docs: remove experimental note from query from deep storage docs (#15132)
(#15157)
Co-authored-by: 317brian <[email protected]>
---
docs/api-reference/sql-api.md | 2 --
docs/querying/query-from-deep-storage.md | 2 --
docs/tutorials/tutorial-query-deep-storage.md | 3 ---
3 files changed, 7 deletions(-)
diff --git a/docs/api-reference/sql-api.md b/docs/api-reference/sql-api.md
index a800f4c8afd..50291c7ba3b 100644
--- a/docs/api-reference/sql-api.md
+++ b/docs/api-reference/sql-api.md
@@ -367,8 +367,6 @@ The following table shows examples of how Druid returns the
column names and dat
## Query from deep storage
-> Query from deep storage is an [experimental
feature](../development/experimental.md).
-
You can use the `sql/statements` endpoint to query segments that exist only in
deep storage and are not loaded onto your Historical processes as determined by
your load rules.
Note that at least one segment of a datasource must be available on a
Historical process so that the Broker can plan your query. A quick way to check
if this is true is whether or not a datasource is visible in the Druid console.
diff --git a/docs/querying/query-from-deep-storage.md
b/docs/querying/query-from-deep-storage.md
index 5f076ca47cd..fba131eba31 100644
--- a/docs/querying/query-from-deep-storage.md
+++ b/docs/querying/query-from-deep-storage.md
@@ -22,8 +22,6 @@ title: "Query from deep storage"
~ under the License.
-->
-> Query from deep storage is an [experimental
feature](../development/experimental.md).
-
Druid can query segments that are only stored in deep storage. Running a query
from deep storage is slower than running queries from segments that are loaded
on Historical processes, but it's a great tool for data that you either access
infrequently or where the low latency results that typical Druid queries
provide is not necessary. Queries from deep storage can increase the surface
area of data available to query without requiring you to scale your Historical
processes to accommodate m [...]
## Keep segments in deep storage only
diff --git a/docs/tutorials/tutorial-query-deep-storage.md
b/docs/tutorials/tutorial-query-deep-storage.md
index 5502ad94228..d4dfe5e6998 100644
--- a/docs/tutorials/tutorial-query-deep-storage.md
+++ b/docs/tutorials/tutorial-query-deep-storage.md
@@ -23,9 +23,6 @@ sidebar_label: "Query from deep storage"
~ under the License.
-->
-
-> Query from deep storage is an [experimental
feature](../development/experimental.md).
-
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
