This is an automated email from the ASF dual-hosted git repository.
kfaraz 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 d69edb7723 Docs: Fix some typos. (#14663)
d69edb7723 is described below
commit d69edb772398b79bcceb1002bbf4eec3991b2cf7
Author: slfan1989 <[email protected]>
AuthorDate: Wed Jul 26 23:54:18 2023 +0800
Docs: Fix some typos. (#14663)
---------
Co-authored-by: slfan1989 <louj1988@@>
---
docs/querying/datasourcemetadataquery.md | 2 +-
docs/querying/multitenancy.md | 2 +-
docs/querying/querying.md | 2 +-
docs/querying/searchquery.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/querying/datasourcemetadataquery.md
b/docs/querying/datasourcemetadataquery.md
index b076671bd5..bdc7128ac8 100644
--- a/docs/querying/datasourcemetadataquery.md
+++ b/docs/querying/datasourcemetadataquery.md
@@ -29,7 +29,7 @@ sidebar_label: "DatasourceMetadata"
Data Source Metadata queries return metadata information for a dataSource.
These queries return information about:
-* The timestamp of latest ingested event for the dataSource. This is the
ingested event without any consideration of rollup.
+* The timestamp of the latest ingested event for the dataSource. This is the
ingested event without any consideration of rollup.
The grammar for these queries is:
diff --git a/docs/querying/multitenancy.md b/docs/querying/multitenancy.md
index 6fc484c241..3619298291 100644
--- a/docs/querying/multitenancy.md
+++ b/docs/querying/multitenancy.md
@@ -75,7 +75,7 @@ stored on this tier.
## Supporting high query concurrency
-Druid uses a [segment](../design/segments.md) as its fundamental unit of
computation. Processes scan segments in parallel and a given process can scan
`druid.processing.numThreads` concurrently. You can add more cores to a cluster
to process more data in parallel and increase performance. Size your Druid
segments such that any computation over any given segment should complete in at
most 500ms. Use the the
[`query/segment/time`](../operations/metrics.md#historical) metric to monitor
com [...]
+Druid uses a [segment](../design/segments.md) as its fundamental unit of
computation. Processes scan segments in parallel and a given process can scan
`druid.processing.numThreads` concurrently. You can add more cores to a cluster
to process more data in parallel and increase performance. Size your Druid
segments such that any computation over any given segment should complete in at
most 500ms. Use the [`query/segment/time`](../operations/metrics.md#historical)
metric to monitor computat [...]
Druid internally stores requests to scan segments in a priority queue. If a
given query requires scanning
more segments than the total number of available processors in a cluster, and
many similarly expensive queries are concurrently
diff --git a/docs/querying/querying.md b/docs/querying/querying.md
index e957e7a527..fe15c9a2bb 100644
--- a/docs/querying/querying.md
+++ b/docs/querying/querying.md
@@ -57,7 +57,7 @@ are designed to be lightweight and complete very quickly.
This means that for mo
more complex visualizations, multiple Druid queries may be required.
Even though queries are typically made to Brokers or Routers, they can also be
accepted by
-[Historical](../design/historical.md) processes and by [Peons (task
JVMs)](../design/peons.md)) that are running
+[Historical](../design/historical.md) processes and by [Peons (task
JVMs)](../design/peons.md) that are running
stream ingestion tasks. This may be valuable if you want to query results for
specific segments that are served by
specific processes.
diff --git a/docs/querying/searchquery.md b/docs/querying/searchquery.md
index 3ee13e78b1..113e1fba94 100644
--- a/docs/querying/searchquery.md
+++ b/docs/querying/searchquery.md
@@ -159,7 +159,7 @@ If any part of a dimension value contains the value
specified in this search que
### `fragment`
-If any part of a dimension value contains all of the values specified in this
search query spec, regardless of case by default, a "match" occurs. The grammar
is:
+If any part of a dimension value contains all the values specified in this
search query spec, regardless of case by default, a "match" occurs. The grammar
is:
```json
{
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
