You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by ab...@apache.org on 2024/01/30 16:02:34 UTC
(druid) branch 29.0.0 updated: Remove documentation for unused segments retrieval API (#15721) (#15798)
This is an automated email from the ASF dual-hosted git repository.
abhishek pushed a commit to branch 29.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/29.0.0 by this push:
new 54dea9672be Remove documentation for unused segments retrieval API (#15721) (#15798)
54dea9672be is described below
commit 54dea9672be8cd409c1caee04c89899d1c06398c
Author: Laksh Singla <la...@gmail.com>
AuthorDate: Tue Jan 30 21:32:28 2024 +0530
Remove documentation for unused segments retrieval API (#15721) (#15798)
* Undocument unused segments retrieval API.
* Mark API deprecated and unstable. Note that it'll be removed.
* Cleanup .spelling entries
* Remove the Unstable annotation
Co-authored-by: Abhishek Radhakrishnan <ab...@gmail.com>
---
docs/api-reference/legacy-metadata-api.md | 10 ----------
website/.spelling | 2 --
2 files changed, 12 deletions(-)
diff --git a/docs/api-reference/legacy-metadata-api.md b/docs/api-reference/legacy-metadata-api.md
index 134ede08d87..453159c1a58 100644
--- a/docs/api-reference/legacy-metadata-api.md
+++ b/docs/api-reference/legacy-metadata-api.md
@@ -248,16 +248,6 @@ Returns full segment metadata for a specific segment in the cluster.
Return the tiers that a datasource exists in.
-`GET /druid/coordinator/v1/datasources/{dataSourceName}/unusedSegments?interval={interval}&limit={limit}&lastSegmentId={lastSegmentId}&sortOrder={sortOrder}`
-
-Returns a list of unused segments for a datasource in the cluster contained within an optionally specified interval.
-Optional parameters for limit and lastSegmentId can be given as well, to limit results and enable paginated results.
-The results may be sorted in either ASC, or DESC order concerning their id, start, and end time, depending on
-specifying the sortOrder parameter. The default behavior in the absence of all optional parameters is to return all
-unused segments for the given datasource in no guaranteed order.
-
-Example usage: `GET /druid/coordinator/v1/datasources/inline_data/unusedSegments?interval=2023-12-01_2023-12-10&limit=10&lastSegmentId=inline_data_2023-12-03T00%3A00%3A00.000Z_2023-12-04T00%3A00%3A00.000Z_2023-12-09T14%3A16%3A53.738Z&sortOrder=ASC}`
-
## Intervals
Note that all _interval_ URL parameters are ISO 8601 strings delimited by a `_` instead of a `/` as in `2016-06-27_2016-06-28`.
diff --git a/website/.spelling b/website/.spelling
index c1df1ee2ffb..640f9887331 100644
--- a/website/.spelling
+++ b/website/.spelling
@@ -374,7 +374,6 @@ kubernetes
kubexit
k8s
laning
-lastSegmentId
lifecycle
localhost
log4j
@@ -504,7 +503,6 @@ Smoosh
smoosh
smooshed
snapshotting
-sortOrder
splittable
ssl
sslmode
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org