This is an automated email from the ASF dual-hosted git repository.

brile 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 246f3df0d83 [backport] docs: fixes spacing issue for a link (#15899)
246f3df0d83 is described below

commit 246f3df0d834c4936707ee6f804a19d037f78e89
Author: 317brian <[email protected]>
AuthorDate: Tue Feb 13 12:52:51 2024 -0800

    [backport] docs: fixes spacing issue for a link (#15899)
    
    Co-authored-by: Peter Marshall <[email protected]>
---
 docs/ingestion/tasks.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ingestion/tasks.md b/docs/ingestion/tasks.md
index 4b3081cef91..8bbbf30b8a2 100644
--- a/docs/ingestion/tasks.md
+++ b/docs/ingestion/tasks.md
@@ -404,7 +404,7 @@ Logs are created by ingestion tasks as they run. You can 
configure Druid to push
 
 Once the task has been submitted to the Overlord it remains `WAITING` for 
locks to be acquired. Worker slot allocation is then `PENDING` until the task 
can actually start executing.
 
-The task then starts creating logs in a local directory of the middle manager 
(or indexer) in a `log` directory for the specific `taskId` at 
[`druid.worker.baseTaskDirs`] 
(../configuration/index.md#middlemanager-configuration).
+The task then starts creating logs in a local directory of the middle manager 
(or indexer) in a `log` directory for the specific `taskId` at 
[`druid.worker.baseTaskDirs`](../configuration/index.md#middlemanager-configuration).
 
 When the task completes - whether it succeeds or fails - the middle manager 
(or indexer) will push the task log file into the location specified in 
[`druid.indexer.logs`](../configuration/index.md#task-logging).
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to