This is an automated email from the ASF dual-hosted git repository.
abhishekrb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/master by this push:
new 947ddd5e297 Fix typos in documentation (#19152)
947ddd5e297 is described below
commit 947ddd5e29761c6ac89d0cf1ed4724980a291f72
Author: Jay Kanakiya <[email protected]>
AuthorDate: Fri Mar 13 10:25:58 2026 -0700
Fix typos in documentation (#19152)
Fixes #18643 and couple of other typos in documentation.
---
docs/configuration/index.md | 2 +-
docs/querying/granularities.md | 2 +-
docs/tutorials/index.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/configuration/index.md b/docs/configuration/index.md
index d870795c536..ece6293e5c5 100644
--- a/docs/configuration/index.md
+++ b/docs/configuration/index.md
@@ -1725,7 +1725,7 @@ This strategy can be enabled by setting
`druid.query.scheduler.prioritization.st
|`druid.query.scheduler.prioritization.durationThreshold`|ISO duration
threshold for maximum duration a queries interval can span before the priority
is automatically adjusted.|none|
|`druid.query.scheduler.prioritization.segmentCountThreshold`|Number threshold
for maximum number of segments that can take part in a query before its
priority is automatically adjusted.|none|
|`druid.query.scheduler.prioritization.segmentRangeThreshold`|ISO duration
threshold for maximum segment range a query can span before the priority is
automatically adjusted.|none|
-|`druid.query.scheduler.prioritization.adjustment`|Amount to reduce the
priority of queries which cross any threshold.|none|
+|`druid.query.scheduler.prioritization.adjustment`|Amount to reduce the
priority of queries which cross any threshold.|5|
##### Laning strategies
diff --git a/docs/querying/granularities.md b/docs/querying/granularities.md
index 6c204df1052..1aa534297ec 100644
--- a/docs/querying/granularities.md
+++ b/docs/querying/granularities.md
@@ -31,7 +31,7 @@ sidebar_label: "Granularities"
:::
Granularity determines how to bucket data across the time dimension, or how to
aggregate data by hour, day, minute, etc and defines how it is stored.
-The granularity formats here apply also to `segmentGranularity` and
`queryGranularity` in the `granularitySpec` section of the the [ingestion
spec](../ingestion/ingestion-spec.md#granularityspec).
+The granularity formats here apply also to `segmentGranularity` and
`queryGranularity` in the `granularitySpec` section of the [ingestion
spec](../ingestion/ingestion-spec.md#granularityspec).
For example, use time granularities in [native queries](querying.md) to bucket
results by time, and in the `dataSchema` \\
[`granularitySpec`](../ingestion/ingestion-spec.md#granularityspec) section of
ingestion specifications to segment incoming data.
diff --git a/docs/tutorials/index.md b/docs/tutorials/index.md
index f55b26e60f6..f270c1b7435 100644
--- a/docs/tutorials/index.md
+++ b/docs/tutorials/index.md
@@ -112,7 +112,7 @@ After starting the Druid services, open the [web
console](../operations/web-cons
It may take a few seconds for all Druid services to finish starting, including
the [Druid router](../design/router.md), which serves the console. If you
attempt to open the web console before startup is complete, you may see errors
in the browser. Wait a few moments and try again.
-In this quickstart, you use the the web console to perform ingestion. The MSQ
task engine specifically uses the **Query** view to edit and run SQL queries.
+In this quickstart, you use the web console to perform ingestion. The MSQ task
engine specifically uses the **Query** view to edit and run SQL queries.
For a complete walkthrough of the **Query** view as it relates to the
multi-stage query architecture and the MSQ task engine, see [UI
walkthrough](../operations/web-console.md).
## Load data
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
