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 aec1d5ddd6b Link fix (#16596)
aec1d5ddd6b is described below
commit aec1d5ddd6bdc582659a9d0371e83a1f03c770dc
Author: Jill Osborne <[email protected]>
AuthorDate: Fri Jun 14 19:40:53 2024 +0100
Link fix (#16596)
* Link fix
* Update docs/operations/auth.md
Co-authored-by: Andreas Maechler <[email protected]>
---------
Co-authored-by: Andreas Maechler <[email protected]>
---
docs/operations/auth.md | 6 +++++-
docs/operations/basic-cluster-tuning.md | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/operations/auth.md b/docs/operations/auth.md
index 9701f632ddb..95b79ef5fa5 100644
--- a/docs/operations/auth.md
+++ b/docs/operations/auth.md
@@ -54,7 +54,11 @@ Druid includes two built-in Authenticators, one of which is
used for the default
### AllowAll authenticator
-This built-in Authenticator authenticates all requests, and always directs
them to an Authorizer named "allowAll". It is not intended to be used for
anything other than the default unsecured configuration.
+This built-in Authenticator authenticates all requests, and always directs
them to an Authorizer named `allowAll`. It's not intended to be used for
anything other than the default unsecured configuration.
+
+```properties
+druid.auth.authorizer.allowAll.type=allowAll
+```
### Anonymous authenticator
diff --git a/docs/operations/basic-cluster-tuning.md
b/docs/operations/basic-cluster-tuning.md
index a9d4e973482..7224276da37 100644
--- a/docs/operations/basic-cluster-tuning.md
+++ b/docs/operations/basic-cluster-tuning.md
@@ -91,7 +91,7 @@ Tuning the cluster so that each Historical can accept 50
queries and 10 non-quer
#### Segment Cache Size
For better query performance, do not allocate segment data to a Historical in
excess of the system free memory. The Historical uses free system memory to
cache segments.
-For more detail, see [Loading and serving segments from
cache](../design/historical/#loading-and-serving-segments-from-cache)
+For more detail, see [Loading and serving segments from
cache](../design/historical.md#loading-and-serving-segments-from-cache).
Druid uses the `druid.segmentCache.locations` to calculate the total segment
data size assigned to a Historical. For rare use cases, you can override this
behavior with `druid.server.maxSize` property.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
