You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by vo...@apache.org on 2022/09/19 02:56:57 UTC
[druid-website] branch asf-site updated: Autobuild (#188)
This is an automated email from the ASF dual-hosted git repository.
vogievetsky pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/druid-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 41b6b3ff Autobuild (#188)
41b6b3ff is described below
commit 41b6b3ffe8f852b3439c17186b0f58fa5f628338
Author: Vadim Ogievetsky <va...@ogievetsky.com>
AuthorDate: Sun Sep 18 19:56:52 2022 -0700
Autobuild (#188)
* Autobuild
* restore files
---
docs/24.0.0/assets/tutorial-quickstart-01.png | Bin 122497 -> 68216 bytes
docs/24.0.0/assets/tutorial-quickstart-03.png | Bin 174445 -> 171269 bytes
docs/24.0.0/configuration/index.html | 6 +++---
docs/24.0.0/data-management/update.html | 6 +++---
.../extensions-core/druid-kerberos.html | 2 +-
docs/24.0.0/ingestion/data-formats.html | 6 +++---
.../ingestion/native-batch-input-sources.html | 4 ++--
docs/24.0.0/misc/math-expr.html | 2 +-
docs/24.0.0/operations/api-reference.html | 4 ++--
docs/24.0.0/operations/clean-metadata-store.html | 2 +-
docs/24.0.0/tutorials/index.html | 15 +++++++++------
docs/latest/assets/tutorial-quickstart-01.png | Bin 122497 -> 68216 bytes
docs/latest/assets/tutorial-quickstart-03.png | Bin 174445 -> 171269 bytes
docs/latest/configuration/index.html | 6 +++---
docs/latest/data-management/update.html | 6 +++---
.../extensions-core/druid-kerberos.html | 2 +-
docs/latest/ingestion/data-formats.html | 6 +++---
.../ingestion/native-batch-input-sources.html | 4 ++--
docs/latest/misc/math-expr.html | 2 +-
docs/latest/operations/api-reference.html | 4 ++--
docs/latest/operations/clean-metadata-store.html | 2 +-
docs/latest/tutorials/index.html | 15 +++++++++------
22 files changed, 50 insertions(+), 44 deletions(-)
diff --git a/docs/24.0.0/assets/tutorial-quickstart-01.png b/docs/24.0.0/assets/tutorial-quickstart-01.png
index 45760eaf..649708b7 100644
Binary files a/docs/24.0.0/assets/tutorial-quickstart-01.png and b/docs/24.0.0/assets/tutorial-quickstart-01.png differ
diff --git a/docs/24.0.0/assets/tutorial-quickstart-03.png b/docs/24.0.0/assets/tutorial-quickstart-03.png
index cff8fecf..917f25d0 100644
Binary files a/docs/24.0.0/assets/tutorial-quickstart-03.png and b/docs/24.0.0/assets/tutorial-quickstart-03.png differ
diff --git a/docs/24.0.0/configuration/index.html b/docs/24.0.0/configuration/index.html
index 876353b8..8305a500 100644
--- a/docs/24.0.0/configuration/index.html
+++ b/docs/24.0.0/configuration/index.html
@@ -1090,7 +1090,7 @@ However, if you need to do it via HTTP, the JSON object can be submitted to the
<pre><code class="hljs">http://<span class="hljs-symbol"><COORDINATOR_IP></span>:<span class="hljs-symbol"><PORT></span>/druid/coordinator/v1/config/<span class="hljs-keyword">history</span>?interval=<span class="hljs-symbol"><interval></span>
</code></pre>
<p>default value of interval can be specified by setting <code>druid.audit.manager.auditHistoryMillis</code> (1 week if not configured) in Coordinator runtime.properties</p>
-<p>To view last <n> entries of the audit history of Coordinator dynamic config issue a GET request to the URL -</p>
+<p>To view last <code>n</code> entries of the audit history of Coordinator dynamic config issue a GET request to the URL -</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><COORDINATOR_IP></span>:<span class="hljs-symbol"><PORT></span>/druid/coordinator/v1/config/<span class="hljs-keyword">history</span>?<span class="hljs-built_in">count</span>=<span class="hljs-symbol"><n></span>
</code></pre>
<h5><a class="anchor" aria-hidden="true" id="lookups-dynamic-configuration"></a><a href="#lookups-dynamic-configuration" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
@@ -1363,7 +1363,7 @@ The below is a list of the supported configurations for auto-compaction.</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><OVERLORD_IP></span>:<span class="hljs-symbol"><port></span>/druid/indexer/v1/worker/<span class="hljs-keyword">history</span>?interval=<span class="hljs-symbol"><interval></span>
</code></pre>
<p>default value of interval can be specified by setting <code>druid.audit.manager.auditHistoryMillis</code> (1 week if not configured) in Overlord runtime.properties.</p>
-<p>To view last <n> entries of the audit history of worker config issue a GET request to the URL -</p>
+<p>To view last <code>n</code> entries of the audit history of worker config issue a GET request to the URL -</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><OVERLORD_IP></span>:<span class="hljs-symbol"><port></span>/druid/indexer/v1/worker/<span class="hljs-keyword">history</span>?<span class="hljs-built_in">count</span>=<span class="hljs-symbol"><n></span>
</code></pre>
<h5><a class="anchor" aria-hidden="true" id="worker-select-strategy"></a><a href="#worker-select-strategy" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -2402,7 +2402,7 @@ context). If query does have <code>maxQueuedBytes</code> in the context, then th
</thead>
<tbody>
<tr><td><code>druid.router.defaultBrokerServiceName</code></td><td>The default Broker to connect to in case service discovery fails.</td><td>druid/broker</td></tr>
-<tr><td><code>druid.router.tierToBrokerMap</code></td><td>Queries for a certain tier of data are routed to their appropriate Broker. This value should be an ordered JSON map of tiers to Broker names. The priority of Brokers is based on the ordering.</td><td>{"_default_tier": "<defaultBrokerServiceName>"}</td></tr>
+<tr><td><code>druid.router.tierToBrokerMap</code></td><td>Queries for a certain tier of data are routed to their appropriate Broker. This value should be an ordered JSON map of tiers to Broker names. The priority of Brokers is based on the ordering.</td><td><code>{"_default_tier": "<defaultBrokerServiceName>"}</code></td></tr>
<tr><td><code>druid.router.defaultRule</code></td><td>The default rule for all datasources.</td><td>"_default"</td></tr>
<tr><td><code>druid.router.pollPeriod</code></td><td>How often to poll for new rules.</td><td>PT1M</td></tr>
<tr><td><code>druid.router.sql.enable</code></td><td>Enable routing of SQL queries using strategies. When<code>true</code>, the Router uses the strategies defined in <code>druid.router.strategies</code> to determine the broker service for a given SQL query. When <code>false</code>, the Router uses the <code>defaultBrokerServiceName</code>.</td><td><code>false</code></td></tr>
diff --git a/docs/24.0.0/data-management/update.html b/docs/24.0.0/data-management/update.html
index fe111793..53fb8dee 100644
--- a/docs/24.0.0/data-management/update.html
+++ b/docs/24.0.0/data-management/update.html
@@ -103,9 +103,9 @@ behaves just like any other <a href="#overwrite">overwrite</a> with regard to at
source</a>. If needed,
<a href="/docs/24.0.0/ingestion/ingestion-spec.html#transformspec"><code>transformSpec</code></a> can be used to filter or modify data during the
reindexing job.</p>
-<p>With SQL, use <a href="/docs/24.0.0/multi-stage-query/reference.html#replace"><code>REPLACE <table> OVERWRITE</code></a> with `SELECT ... FROM</p>
-<table>`. (Druid does not have `UPDATE` or `ALTER TABLE` statements.) Any SQL SELECT query can be used to filter,
-modify, or enrich the data during the reindexing job.
+<p>With SQL, use <a href="/docs/24.0.0/multi-stage-query/reference.html#replace"><code>REPLACE <table> OVERWRITE</code></a> with <code>SELECT ... FROM <table></code>.
+(Druid does not have <code>UPDATE</code> or <code>ALTER TABLE</code> statements.) Any SQL SELECT query can be used to filter,
+modify, or enrich the data during the reindexing job.</p>
<h2><a class="anchor" aria-hidden="true" id="rolled-up-datasources"></a><a href="#rolled-up-datasources" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2 [...]
<p>Rolled-up datasources can be effectively updated using appends, without rewrites. When you append a row that has an
identical set of dimensions to an existing row, queries that use aggregation operators automatically combine those two
diff --git a/docs/24.0.0/development/extensions-core/druid-kerberos.html b/docs/24.0.0/development/extensions-core/druid-kerberos.html
index 95e781cd..dce12991 100644
--- a/docs/24.0.0/development/extensions-core/druid-kerberos.html
+++ b/docs/24.0.0/development/extensions-core/druid-kerberos.html
@@ -100,7 +100,7 @@ Make sure to <a href="/docs/24.0.0/development/extensions.html#loading-extension
<tr><td><code>druid.auth.authenticator.kerberos.serverPrincipal</code></td><td><code>HTTP/_HOST@EXAMPLE.COM</code></td><td>SPNEGO service principal used by druid processes</td><td>empty</td><td>Yes</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.serverKeytab</code></td><td><code>/etc/security/keytabs/spnego.service.keytab</code></td><td>SPNego service keytab used by druid processes</td><td>empty</td><td>Yes</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.authToLocal</code></td><td><code>RULE:[1:$1@$0](druid@EXAMPLE.COM)s/.*/druid DEFAULT</code></td><td>It allows you to set a general rule for mapping principal names to local user names. It will be used if there is not an explicit mapping for the principal name that is being translated.</td><td>DEFAULT</td><td>No</td></tr>
-<tr><td><code>druid.auth.authenticator.kerberos.cookieSignatureSecret</code></td><td><code>secretString</code></td><td>Secret used to sign authentication cookies. It is advisable to explicitly set it, if you have multiple druid nodes running on same machine with different ports as the Cookie Specification does not guarantee isolation by port.</td><td><Random value></td><td>No</td></tr>
+<tr><td><code>druid.auth.authenticator.kerberos.cookieSignatureSecret</code></td><td><code>secretString</code></td><td>Secret used to sign authentication cookies. It is advisable to explicitly set it, if you have multiple druid nodes running on same machine with different ports as the Cookie Specification does not guarantee isolation by port.</td><td>Random value</td><td>No</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.authorizerName</code></td><td>Depends on available authorizers</td><td>Authorizer that requests should be directed to</td><td>Empty</td><td>Yes</td></tr>
</tbody>
</table>
diff --git a/docs/24.0.0/ingestion/data-formats.html b/docs/24.0.0/ingestion/data-formats.html
index c8804437..be86b502 100644
--- a/docs/24.0.0/ingestion/data-formats.html
+++ b/docs/24.0.0/ingestion/data-formats.html
@@ -465,7 +465,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td>type</td><td>String</td><td>Set value to <code>schema_registry</code>.</td><td>no</td></tr>
<tr><td>url</td><td>String</td><td>Specifies the URL endpoint of the Schema Registry.</td><td>yes</td></tr>
<tr><td>capacity</td><td>Integer</td><td>Specifies the max size of the cache (default = Integer.MAX_VALUE).</td><td>no</td></tr>
-<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
+<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
<tr><td>config</td><td>Json</td><td>To send additional configurations, configured for Schema Registry. This can be supplied via a <a href="/docs/24.0.0/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
<tr><td>headers</td><td>Json</td><td>To send headers to the Schema Registry. This can be supplied via a <a href="/docs/24.0.0/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
</tbody>
@@ -664,7 +664,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td style="text-align:left">sum()</td><td style="text-align:left">Provides the sum value of an array of numbers</td><td style="text-align:left">Double</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td></tr>
<tr><td style="text-align:left">concat(X)</td><td style="text-align:left">Provides a concatenated version of the path output with a new item</td><td style="text-align:left">like input</td><td style="text-align:left">✓</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
<tr><td style="text-align:left">append(X)</td><td style="text-align:left">add an item to the json path output array</td><td style="text-align:left">like input</td><td style="text-align:left">✓</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
-<tr><td style="text-align:left">keys()</td><td style="text-align:left">Provides the property keys (An alternative for terminal tilde ~)</td><td style="text-align:left">Set<E></td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
+<tr><td style="text-align:left">keys()</td><td style="text-align:left">Provides the property keys (An alternative for terminal tilde ~)</td><td style="text-align:left">Set<E></td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
</tbody>
</table>
</li>
@@ -1311,7 +1311,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td>type</td><td>String</td><td>Set value to <code>schema_registry</code>.</td><td>yes</td></tr>
<tr><td>url</td><td>String</td><td>Specifies the URL endpoint of the Schema Registry.</td><td>yes</td></tr>
<tr><td>capacity</td><td>Integer</td><td>Specifies the max size of the cache (default = Integer.MAX_VALUE).</td><td>no</td></tr>
-<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
+<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
<tr><td>config</td><td>Json</td><td>To send additional configurations, configured for Schema Registry. This can be supplied via a <a href="/docs/24.0.0/operations/dynamic-config-provider.html">DynamicConfigProvider</a>.</td><td>no</td></tr>
<tr><td>headers</td><td>Json</td><td>To send headers to the Schema Registry. This can be supplied via a <a href="/docs/24.0.0/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
</tbody>
diff --git a/docs/24.0.0/ingestion/native-batch-input-sources.html b/docs/24.0.0/ingestion/native-batch-input-sources.html
index 20518374..79273968 100644
--- a/docs/24.0.0/ingestion/native-batch-input-sources.html
+++ b/docs/24.0.0/ingestion/native-batch-input-sources.html
@@ -385,8 +385,8 @@ specify objects as a list of file URI strings or prefixes. You can split the Azu
</thead>
<tbody>
<tr><td>type</td><td>Set the value to <code>azure</code>.</td><td>None</td><td>yes</td></tr>
-<tr><td>uris</td><td>JSON array of URIs where the Azure objects to be ingested are located, in the form "azure://<container>/<path-to-file>"</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
-<tr><td>prefixes</td><td>JSON array of URI prefixes for the locations of Azure objects to ingest, in the form <code>azure://\<container>/\<prefix\></code>. Empty objects starting with one of the given prefixes are skipped.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
+<tr><td>uris</td><td>JSON array of URIs where the Azure objects to be ingested are located, in the form <code>azure://<container>/<path-to-file></code></td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
+<tr><td>prefixes</td><td>JSON array of URI prefixes for the locations of Azure objects to ingest, in the form <code>azure://<container>/<prefix></code>. Empty objects starting with one of the given prefixes are skipped.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
<tr><td>objects</td><td>JSON array of Azure objects to ingest.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
</tbody>
</table>
diff --git a/docs/24.0.0/misc/math-expr.html b/docs/24.0.0/misc/math-expr.html
index cc797ac0..a944ccfd 100644
--- a/docs/24.0.0/misc/math-expr.html
+++ b/docs/24.0.0/misc/math-expr.html
@@ -117,7 +117,7 @@ also generated by most <a href="/docs/24.0.0/querying/sql-scalar.html">Druid SQL
<tr><th>name</th><th>description</th></tr>
</thead>
<tbody>
-<tr><td>cast</td><td>cast(expr,'LONG' or 'DOUBLE' or 'STRING' or 'ARRAY<LONG>', or 'ARRAY<DOUBLE>' or 'ARRAY<STRING>') returns expr with specified type. exception can be thrown. Scalar types may be cast to array types and will take the form of a single element list (null will still be null).</td></tr>
+<tr><td>cast</td><td>cast(expr,LONG or DOUBLE or STRING or ARRAY<LONG>, or ARRAY<DOUBLE> or ARRAY<STRING>) returns expr with specified type. exception can be thrown. Scalar types may be cast to array types and will take the form of a single element list (null will still be null).</td></tr>
<tr><td>if</td><td>if(predicate,then,else) returns 'then' if 'predicate' evaluates to a positive number, otherwise it returns 'else'</td></tr>
<tr><td>nvl</td><td>nvl(expr,expr-for-null) returns 'expr-for-null' if 'expr' is null (or empty string for string type)</td></tr>
<tr><td>like</td><td>like(expr, pattern[, escape]) is equivalent to SQL <code>expr LIKE pattern</code></td></tr>
diff --git a/docs/24.0.0/operations/api-reference.html b/docs/24.0.0/operations/api-reference.html
index 641eb88b..ee293e7d 100644
--- a/docs/24.0.0/operations/api-reference.html
+++ b/docs/24.0.0/operations/api-reference.html
@@ -413,7 +413,7 @@ result of this API call.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/history?count=<n></code></li>
</ul>
-<p>Returns last <n> entries of audit history of rules for all datasources.</p>
+<p>Returns last <code>n</code> entries of audit history of rules for all datasources.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}/history?interval=<interval></code></li>
</ul>
@@ -421,7 +421,7 @@ result of this API call.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}/history?count=<n></code></li>
</ul>
-<p>Returns last <n> entries of audit history of rules for a specified datasource.</p>
+<p>Returns last <code>n</code> entries of audit history of rules for a specified datasource.</p>
<h5><a class="anchor" aria-hidden="true" id="post-2"></a><a href="#post-2" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}</code></li>
diff --git a/docs/24.0.0/operations/clean-metadata-store.html b/docs/24.0.0/operations/clean-metadata-store.html
index ac0f97e7..54bff599 100644
--- a/docs/24.0.0/operations/clean-metadata-store.html
+++ b/docs/24.0.0/operations/clean-metadata-store.html
@@ -114,7 +114,7 @@ Define the properties in the <code>coordinator/runtime.properties</code> file.</
</ul>
<p>For details on configuration properties, see <a href="/docs/24.0.0/configuration/index.html#metadata-management">Metadata management</a>.
If you want to skip the details, check out the <a href="#example">example</a> for configuring automated metadata cleanup.</p>
-<p><a name="kill-task"></p>
+<p><a name="kill-task"></a></p>
<h3><a class="anchor" aria-hidden="true" id="segment-records-and-segments-in-deep-storage-kill-task"></a><a href="#segment-records-and-segments-in-deep-storage-kill-task" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 [...]
<blockquote>
<p>The kill task is the only configuration in this topic that affects actual data in deep storage and not simply metadata or logs.</p>
diff --git a/docs/24.0.0/tutorials/index.html b/docs/24.0.0/tutorials/index.html
index 33ad5852..4fff41ca 100644
--- a/docs/24.0.0/tutorials/index.html
+++ b/docs/24.0.0/tutorials/index.html
@@ -123,12 +123,15 @@ This configuration includes default settings that are appropriate for this tutor
</code></pre>
<p>This brings up instances of ZooKeeper and the Druid services:</p>
<pre><code class="hljs css language-bash">$ ./bin/start-micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[zk], logging to[/apache-druid-24.0.0/var/sv/zk.log]: bin/run-zk conf
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[coordinator-overlord], logging to[/apache-druid-24.0.0/var/sv/coordinator-overlord.log]: bin/run-druid coordinator-overlord conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[broker], logging to[/apache-druid-24.0.0/var/sv/broker.log]: bin/run-druid broker conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[router], logging to[/apache-druid-24.0.0/var/sv/router.log]: bin/run-druid router conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[historical], logging to[/apache-druid-24.0.0/var/sv/historical.log]: bin/run-druid historical conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[middleManager], logging to[/apache-druid-24.0.0/var/sv/middleManager.log]: bin/run-druid middleManager conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Starting Apache Druid.
+[Thu Sep 8 18:30:00 2022] Open http://localhost:8888/ <span class="hljs-keyword">in</span> your browser to access the web console.
+[Thu Sep 8 18:30:00 2022] Or, <span class="hljs-keyword">if</span> you have enabled TLS, use https on port 9088.
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[zk], logging to[/apache-druid-24.0.0/var/sv/zk.log]: bin/run-zk conf
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[coordinator-overlord], logging to[/apache-druid-24.0.0/var/sv/coordinator-overlord.log]: bin/run-druid coordinator-overlord conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[broker], logging to[/apache-druid-24.0.0/var/sv/broker.log]: bin/run-druid broker conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[router], logging to[/apache-druid-24.0.0/var/sv/router.log]: bin/run-druid router conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[historical], logging to[/apache-druid-24.0.0/var/sv/historical.log]: bin/run-druid historical conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[middleManager], logging to[/apache-druid-24.0.0/var/sv/middleManager.log]: bin/run-druid middleManager conf/druid/single-server/micro-quickstart
</code></pre>
<p>All persistent state, such as the cluster metadata store and segments for the services, are kept in the <code>var</code> directory under
the Druid root directory, apache-druid-24.0.0. Each service writes to a log file under <code>var/sv</code>.</p>
diff --git a/docs/latest/assets/tutorial-quickstart-01.png b/docs/latest/assets/tutorial-quickstart-01.png
index 45760eaf..649708b7 100644
Binary files a/docs/latest/assets/tutorial-quickstart-01.png and b/docs/latest/assets/tutorial-quickstart-01.png differ
diff --git a/docs/latest/assets/tutorial-quickstart-03.png b/docs/latest/assets/tutorial-quickstart-03.png
index cff8fecf..917f25d0 100644
Binary files a/docs/latest/assets/tutorial-quickstart-03.png and b/docs/latest/assets/tutorial-quickstart-03.png differ
diff --git a/docs/latest/configuration/index.html b/docs/latest/configuration/index.html
index ad124502..dd3d44b6 100644
--- a/docs/latest/configuration/index.html
+++ b/docs/latest/configuration/index.html
@@ -1090,7 +1090,7 @@ However, if you need to do it via HTTP, the JSON object can be submitted to the
<pre><code class="hljs">http://<span class="hljs-symbol"><COORDINATOR_IP></span>:<span class="hljs-symbol"><PORT></span>/druid/coordinator/v1/config/<span class="hljs-keyword">history</span>?interval=<span class="hljs-symbol"><interval></span>
</code></pre>
<p>default value of interval can be specified by setting <code>druid.audit.manager.auditHistoryMillis</code> (1 week if not configured) in Coordinator runtime.properties</p>
-<p>To view last <n> entries of the audit history of Coordinator dynamic config issue a GET request to the URL -</p>
+<p>To view last <code>n</code> entries of the audit history of Coordinator dynamic config issue a GET request to the URL -</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><COORDINATOR_IP></span>:<span class="hljs-symbol"><PORT></span>/druid/coordinator/v1/config/<span class="hljs-keyword">history</span>?<span class="hljs-built_in">count</span>=<span class="hljs-symbol"><n></span>
</code></pre>
<h5><a class="anchor" aria-hidden="true" id="lookups-dynamic-configuration"></a><a href="#lookups-dynamic-configuration" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
@@ -1363,7 +1363,7 @@ The below is a list of the supported configurations for auto-compaction.</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><OVERLORD_IP></span>:<span class="hljs-symbol"><port></span>/druid/indexer/v1/worker/<span class="hljs-keyword">history</span>?interval=<span class="hljs-symbol"><interval></span>
</code></pre>
<p>default value of interval can be specified by setting <code>druid.audit.manager.auditHistoryMillis</code> (1 week if not configured) in Overlord runtime.properties.</p>
-<p>To view last <n> entries of the audit history of worker config issue a GET request to the URL -</p>
+<p>To view last <code>n</code> entries of the audit history of worker config issue a GET request to the URL -</p>
<pre><code class="hljs">http://<span class="hljs-symbol"><OVERLORD_IP></span>:<span class="hljs-symbol"><port></span>/druid/indexer/v1/worker/<span class="hljs-keyword">history</span>?<span class="hljs-built_in">count</span>=<span class="hljs-symbol"><n></span>
</code></pre>
<h5><a class="anchor" aria-hidden="true" id="worker-select-strategy"></a><a href="#worker-select-strategy" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -2402,7 +2402,7 @@ context). If query does have <code>maxQueuedBytes</code> in the context, then th
</thead>
<tbody>
<tr><td><code>druid.router.defaultBrokerServiceName</code></td><td>The default Broker to connect to in case service discovery fails.</td><td>druid/broker</td></tr>
-<tr><td><code>druid.router.tierToBrokerMap</code></td><td>Queries for a certain tier of data are routed to their appropriate Broker. This value should be an ordered JSON map of tiers to Broker names. The priority of Brokers is based on the ordering.</td><td>{"_default_tier": "<defaultBrokerServiceName>"}</td></tr>
+<tr><td><code>druid.router.tierToBrokerMap</code></td><td>Queries for a certain tier of data are routed to their appropriate Broker. This value should be an ordered JSON map of tiers to Broker names. The priority of Brokers is based on the ordering.</td><td><code>{"_default_tier": "<defaultBrokerServiceName>"}</code></td></tr>
<tr><td><code>druid.router.defaultRule</code></td><td>The default rule for all datasources.</td><td>"_default"</td></tr>
<tr><td><code>druid.router.pollPeriod</code></td><td>How often to poll for new rules.</td><td>PT1M</td></tr>
<tr><td><code>druid.router.sql.enable</code></td><td>Enable routing of SQL queries using strategies. When<code>true</code>, the Router uses the strategies defined in <code>druid.router.strategies</code> to determine the broker service for a given SQL query. When <code>false</code>, the Router uses the <code>defaultBrokerServiceName</code>.</td><td><code>false</code></td></tr>
diff --git a/docs/latest/data-management/update.html b/docs/latest/data-management/update.html
index b39c88ab..427ce28e 100644
--- a/docs/latest/data-management/update.html
+++ b/docs/latest/data-management/update.html
@@ -103,9 +103,9 @@ behaves just like any other <a href="#overwrite">overwrite</a> with regard to at
source</a>. If needed,
<a href="/docs/latest/ingestion/ingestion-spec.html#transformspec"><code>transformSpec</code></a> can be used to filter or modify data during the
reindexing job.</p>
-<p>With SQL, use <a href="/docs/latest/multi-stage-query/reference.html#replace"><code>REPLACE <table> OVERWRITE</code></a> with `SELECT ... FROM</p>
-<table>`. (Druid does not have `UPDATE` or `ALTER TABLE` statements.) Any SQL SELECT query can be used to filter,
-modify, or enrich the data during the reindexing job.
+<p>With SQL, use <a href="/docs/latest/multi-stage-query/reference.html#replace"><code>REPLACE <table> OVERWRITE</code></a> with <code>SELECT ... FROM <table></code>.
+(Druid does not have <code>UPDATE</code> or <code>ALTER TABLE</code> statements.) Any SQL SELECT query can be used to filter,
+modify, or enrich the data during the reindexing job.</p>
<h2><a class="anchor" aria-hidden="true" id="rolled-up-datasources"></a><a href="#rolled-up-datasources" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2 [...]
<p>Rolled-up datasources can be effectively updated using appends, without rewrites. When you append a row that has an
identical set of dimensions to an existing row, queries that use aggregation operators automatically combine those two
diff --git a/docs/latest/development/extensions-core/druid-kerberos.html b/docs/latest/development/extensions-core/druid-kerberos.html
index 3551509c..2b86f5a7 100644
--- a/docs/latest/development/extensions-core/druid-kerberos.html
+++ b/docs/latest/development/extensions-core/druid-kerberos.html
@@ -100,7 +100,7 @@ Make sure to <a href="/docs/latest/development/extensions.html#loading-extension
<tr><td><code>druid.auth.authenticator.kerberos.serverPrincipal</code></td><td><code>HTTP/_HOST@EXAMPLE.COM</code></td><td>SPNEGO service principal used by druid processes</td><td>empty</td><td>Yes</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.serverKeytab</code></td><td><code>/etc/security/keytabs/spnego.service.keytab</code></td><td>SPNego service keytab used by druid processes</td><td>empty</td><td>Yes</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.authToLocal</code></td><td><code>RULE:[1:$1@$0](druid@EXAMPLE.COM)s/.*/druid DEFAULT</code></td><td>It allows you to set a general rule for mapping principal names to local user names. It will be used if there is not an explicit mapping for the principal name that is being translated.</td><td>DEFAULT</td><td>No</td></tr>
-<tr><td><code>druid.auth.authenticator.kerberos.cookieSignatureSecret</code></td><td><code>secretString</code></td><td>Secret used to sign authentication cookies. It is advisable to explicitly set it, if you have multiple druid nodes running on same machine with different ports as the Cookie Specification does not guarantee isolation by port.</td><td><Random value></td><td>No</td></tr>
+<tr><td><code>druid.auth.authenticator.kerberos.cookieSignatureSecret</code></td><td><code>secretString</code></td><td>Secret used to sign authentication cookies. It is advisable to explicitly set it, if you have multiple druid nodes running on same machine with different ports as the Cookie Specification does not guarantee isolation by port.</td><td>Random value</td><td>No</td></tr>
<tr><td><code>druid.auth.authenticator.kerberos.authorizerName</code></td><td>Depends on available authorizers</td><td>Authorizer that requests should be directed to</td><td>Empty</td><td>Yes</td></tr>
</tbody>
</table>
diff --git a/docs/latest/ingestion/data-formats.html b/docs/latest/ingestion/data-formats.html
index 3644267b..92356a42 100644
--- a/docs/latest/ingestion/data-formats.html
+++ b/docs/latest/ingestion/data-formats.html
@@ -465,7 +465,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td>type</td><td>String</td><td>Set value to <code>schema_registry</code>.</td><td>no</td></tr>
<tr><td>url</td><td>String</td><td>Specifies the URL endpoint of the Schema Registry.</td><td>yes</td></tr>
<tr><td>capacity</td><td>Integer</td><td>Specifies the max size of the cache (default = Integer.MAX_VALUE).</td><td>no</td></tr>
-<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
+<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
<tr><td>config</td><td>Json</td><td>To send additional configurations, configured for Schema Registry. This can be supplied via a <a href="/docs/latest/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
<tr><td>headers</td><td>Json</td><td>To send headers to the Schema Registry. This can be supplied via a <a href="/docs/latest/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
</tbody>
@@ -664,7 +664,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td style="text-align:left">sum()</td><td style="text-align:left">Provides the sum value of an array of numbers</td><td style="text-align:left">Double</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td><td style="text-align:left">✓</td></tr>
<tr><td style="text-align:left">concat(X)</td><td style="text-align:left">Provides a concatenated version of the path output with a new item</td><td style="text-align:left">like input</td><td style="text-align:left">✓</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
<tr><td style="text-align:left">append(X)</td><td style="text-align:left">add an item to the json path output array</td><td style="text-align:left">like input</td><td style="text-align:left">✓</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
-<tr><td style="text-align:left">keys()</td><td style="text-align:left">Provides the property keys (An alternative for terminal tilde ~)</td><td style="text-align:left">Set<E></td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
+<tr><td style="text-align:left">keys()</td><td style="text-align:left">Provides the property keys (An alternative for terminal tilde ~)</td><td style="text-align:left">Set<E></td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td><td style="text-align:left">✗</td></tr>
</tbody>
</table>
</li>
@@ -1311,7 +1311,7 @@ For details, see the Schema Registry <a href="http://docs.confluent.io/current/s
<tr><td>type</td><td>String</td><td>Set value to <code>schema_registry</code>.</td><td>yes</td></tr>
<tr><td>url</td><td>String</td><td>Specifies the URL endpoint of the Schema Registry.</td><td>yes</td></tr>
<tr><td>capacity</td><td>Integer</td><td>Specifies the max size of the cache (default = Integer.MAX_VALUE).</td><td>no</td></tr>
-<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
+<tr><td>urls</td><td>Array<String></td><td>Specifies the URL endpoints of the multiple Schema Registry instances.</td><td>yes (if <code>url</code> is not provided)</td></tr>
<tr><td>config</td><td>Json</td><td>To send additional configurations, configured for Schema Registry. This can be supplied via a <a href="/docs/latest/operations/dynamic-config-provider.html">DynamicConfigProvider</a>.</td><td>no</td></tr>
<tr><td>headers</td><td>Json</td><td>To send headers to the Schema Registry. This can be supplied via a <a href="/docs/latest/operations/dynamic-config-provider.html">DynamicConfigProvider</a></td><td>no</td></tr>
</tbody>
diff --git a/docs/latest/ingestion/native-batch-input-sources.html b/docs/latest/ingestion/native-batch-input-sources.html
index 8f3c92c5..947e4561 100644
--- a/docs/latest/ingestion/native-batch-input-sources.html
+++ b/docs/latest/ingestion/native-batch-input-sources.html
@@ -385,8 +385,8 @@ specify objects as a list of file URI strings or prefixes. You can split the Azu
</thead>
<tbody>
<tr><td>type</td><td>Set the value to <code>azure</code>.</td><td>None</td><td>yes</td></tr>
-<tr><td>uris</td><td>JSON array of URIs where the Azure objects to be ingested are located, in the form "azure://<container>/<path-to-file>"</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
-<tr><td>prefixes</td><td>JSON array of URI prefixes for the locations of Azure objects to ingest, in the form <code>azure://\<container>/\<prefix\></code>. Empty objects starting with one of the given prefixes are skipped.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
+<tr><td>uris</td><td>JSON array of URIs where the Azure objects to be ingested are located, in the form <code>azure://<container>/<path-to-file></code></td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
+<tr><td>prefixes</td><td>JSON array of URI prefixes for the locations of Azure objects to ingest, in the form <code>azure://<container>/<prefix></code>. Empty objects starting with one of the given prefixes are skipped.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
<tr><td>objects</td><td>JSON array of Azure objects to ingest.</td><td>None</td><td><code>uris</code> or <code>prefixes</code> or <code>objects</code> must be set</td></tr>
</tbody>
</table>
diff --git a/docs/latest/misc/math-expr.html b/docs/latest/misc/math-expr.html
index ba83aa0e..7b5c3918 100644
--- a/docs/latest/misc/math-expr.html
+++ b/docs/latest/misc/math-expr.html
@@ -117,7 +117,7 @@ also generated by most <a href="/docs/latest/querying/sql-scalar.html">Druid SQL
<tr><th>name</th><th>description</th></tr>
</thead>
<tbody>
-<tr><td>cast</td><td>cast(expr,'LONG' or 'DOUBLE' or 'STRING' or 'ARRAY<LONG>', or 'ARRAY<DOUBLE>' or 'ARRAY<STRING>') returns expr with specified type. exception can be thrown. Scalar types may be cast to array types and will take the form of a single element list (null will still be null).</td></tr>
+<tr><td>cast</td><td>cast(expr,LONG or DOUBLE or STRING or ARRAY<LONG>, or ARRAY<DOUBLE> or ARRAY<STRING>) returns expr with specified type. exception can be thrown. Scalar types may be cast to array types and will take the form of a single element list (null will still be null).</td></tr>
<tr><td>if</td><td>if(predicate,then,else) returns 'then' if 'predicate' evaluates to a positive number, otherwise it returns 'else'</td></tr>
<tr><td>nvl</td><td>nvl(expr,expr-for-null) returns 'expr-for-null' if 'expr' is null (or empty string for string type)</td></tr>
<tr><td>like</td><td>like(expr, pattern[, escape]) is equivalent to SQL <code>expr LIKE pattern</code></td></tr>
diff --git a/docs/latest/operations/api-reference.html b/docs/latest/operations/api-reference.html
index c4355b0f..8a226551 100644
--- a/docs/latest/operations/api-reference.html
+++ b/docs/latest/operations/api-reference.html
@@ -413,7 +413,7 @@ result of this API call.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/history?count=<n></code></li>
</ul>
-<p>Returns last <n> entries of audit history of rules for all datasources.</p>
+<p>Returns last <code>n</code> entries of audit history of rules for all datasources.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}/history?interval=<interval></code></li>
</ul>
@@ -421,7 +421,7 @@ result of this API call.</p>
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}/history?count=<n></code></li>
</ul>
-<p>Returns last <n> entries of audit history of rules for a specified datasource.</p>
+<p>Returns last <code>n</code> entries of audit history of rules for a specified datasource.</p>
<h5><a class="anchor" aria-hidden="true" id="post-2"></a><a href="#post-2" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<ul>
<li><code>/druid/coordinator/v1/rules/{dataSourceName}</code></li>
diff --git a/docs/latest/operations/clean-metadata-store.html b/docs/latest/operations/clean-metadata-store.html
index 42b5faac..b66d0f8a 100644
--- a/docs/latest/operations/clean-metadata-store.html
+++ b/docs/latest/operations/clean-metadata-store.html
@@ -114,7 +114,7 @@ Define the properties in the <code>coordinator/runtime.properties</code> file.</
</ul>
<p>For details on configuration properties, see <a href="/docs/latest/configuration/index.html#metadata-management">Metadata management</a>.
If you want to skip the details, check out the <a href="#example">example</a> for configuring automated metadata cleanup.</p>
-<p><a name="kill-task"></p>
+<p><a name="kill-task"></a></p>
<h3><a class="anchor" aria-hidden="true" id="segment-records-and-segments-in-deep-storage-kill-task"></a><a href="#segment-records-and-segments-in-deep-storage-kill-task" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 [...]
<blockquote>
<p>The kill task is the only configuration in this topic that affects actual data in deep storage and not simply metadata or logs.</p>
diff --git a/docs/latest/tutorials/index.html b/docs/latest/tutorials/index.html
index e3320f7e..fd43cb3c 100644
--- a/docs/latest/tutorials/index.html
+++ b/docs/latest/tutorials/index.html
@@ -123,12 +123,15 @@ This configuration includes default settings that are appropriate for this tutor
</code></pre>
<p>This brings up instances of ZooKeeper and the Druid services:</p>
<pre><code class="hljs css language-bash">$ ./bin/start-micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[zk], logging to[/apache-druid-24.0.0/var/sv/zk.log]: bin/run-zk conf
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[coordinator-overlord], logging to[/apache-druid-24.0.0/var/sv/coordinator-overlord.log]: bin/run-druid coordinator-overlord conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[broker], logging to[/apache-druid-24.0.0/var/sv/broker.log]: bin/run-druid broker conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[router], logging to[/apache-druid-24.0.0/var/sv/router.log]: bin/run-druid router conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[historical], logging to[/apache-druid-24.0.0/var/sv/historical.log]: bin/run-druid historical conf/druid/single-server/micro-quickstart
-[Fri May 3 11:40:50 2019] Running <span class="hljs-built_in">command</span>[middleManager], logging to[/apache-druid-24.0.0/var/sv/middleManager.log]: bin/run-druid middleManager conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Starting Apache Druid.
+[Thu Sep 8 18:30:00 2022] Open http://localhost:8888/ <span class="hljs-keyword">in</span> your browser to access the web console.
+[Thu Sep 8 18:30:00 2022] Or, <span class="hljs-keyword">if</span> you have enabled TLS, use https on port 9088.
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[zk], logging to[/apache-druid-24.0.0/var/sv/zk.log]: bin/run-zk conf
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[coordinator-overlord], logging to[/apache-druid-24.0.0/var/sv/coordinator-overlord.log]: bin/run-druid coordinator-overlord conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[broker], logging to[/apache-druid-24.0.0/var/sv/broker.log]: bin/run-druid broker conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[router], logging to[/apache-druid-24.0.0/var/sv/router.log]: bin/run-druid router conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[historical], logging to[/apache-druid-24.0.0/var/sv/historical.log]: bin/run-druid historical conf/druid/single-server/micro-quickstart
+[Thu Sep 8 18:30:00 2022] Running <span class="hljs-built_in">command</span>[middleManager], logging to[/apache-druid-24.0.0/var/sv/middleManager.log]: bin/run-druid middleManager conf/druid/single-server/micro-quickstart
</code></pre>
<p>All persistent state, such as the cluster metadata store and segments for the services, are kept in the <code>var</code> directory under
the Druid root directory, apache-druid-24.0.0. Each service writes to a log file under <code>var/sv</code>.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org