Merge pull request #769 from kgyrtkirk/up-5fee4e1960a214731616c1aab1f3de657e22e5f3

Upstream: 5fee4e1

Author: kgyrtkirk

.github/workflows/static-checks.yml

@@ -160,7 +160,7 @@ jobs:
       - name: setup node
         uses: actions/setup-node@v3
         with:
-          node-version: 16.17.0
+          node-version: 18.0.0
 
       - name: docs
         run: |

benchmarks/src/test/java/org/apache/druid/server/coordinator/NewestSegmentFirstPolicyBenchmark.java

@@ -93,7 +93,7 @@ public void setup()
       final String dataSource = DATA_SOURCE_PREFIX + i;
       compactionConfigs.put(
           dataSource,
-          DataSourceCompactionConfig
+          InlineSchemaDataSourceCompactionConfig
               .builder()
               .forDataSource(dataSource)
               .withTaskPriority(0)

distribution/bin/check-licenses.py

@@ -310,6 +310,7 @@ def build_compatible_license_names():
     compatible_licenses['SPDX-License-Identifier: MIT'] = 'MIT License'
 
     compatible_licenses['The Go license'] = 'The Go license'
+    compatible_licenses['Universal Permissive License, Version 1.0'] = 'Universal Permissive License, Version 1.0'
 
     compatible_licenses['-'] = '-'
     return compatible_licenses

docs/api-reference/sql-ingestion-api.md

@@ -379,7 +379,8 @@ print(response.text)
 
 The response shows an example report for a query.
 
-<details><summary>View the response</summary>
+<details>
+<summary>View the response</summary>
 
 ```json
 {

docs/comparisons/druid-vs-spark.md

@@ -39,4 +39,4 @@ One typical setup seen in production is to process data in Spark, and load the p
 
 For more information about using Druid and Spark together, including benchmarks of the two systems, please see:
 
-<https://www.linkedin.com/pulse/combining-druid-spark-interactive-flexible-analytics-scale-butani>
+https://www.linkedin.com/pulse/combining-druid-spark-interactive-flexible-analytics-scale-butani

docs/configuration/extensions.md

@@ -101,7 +101,7 @@ All of these community extensions can be downloaded using [pull-deps](../operati
 |druid-momentsketch|Support for approximate quantile queries using the [momentsketch](https://github.com/stanford-futuredata/momentsketch) library|[link](../development/extensions-contrib/momentsketch-quantiles.md)|
 |druid-tdigestsketch|Support for approximate sketch aggregators based on [T-Digest](https://github.com/tdunning/t-digest)|[link](../development/extensions-contrib/tdigestsketch-quantiles.md)|
 |gce-extensions|GCE Extensions|[link](../development/extensions-contrib/gce-extensions.md)|
-|prometheus-emitter|Exposes [Druid metrics](../operations/metrics.md) for Prometheus server collection (<https://prometheus.io/>)|[link](../development/extensions-contrib/prometheus.md)|
+|prometheus-emitter|Exposes [Druid metrics](../operations/metrics.md) for [Prometheus](https://prometheus.io/)|[link](../development/extensions-contrib/prometheus.md)|
 |druid-spectator-histogram|Support for efficient approximate percentile queries|[link](../development/extensions-contrib/spectator-histogram.md)|
 |druid-rabbit-indexing-service|Support for creating and managing [RabbitMQ](https://www.rabbitmq.com/) indexing tasks|[link](../development/extensions-contrib/rabbit-stream-ingestion.md)|
 |druid-ranger-security|Support for access control through Apache Ranger.|[link](../development/extensions-contrib/druid-ranger-security.md)|

docs/configuration/index.md

@@ -403,7 +403,7 @@ Metric monitoring is an essential part of Druid operations. The following monito
 |`org.apache.druid.server.metrics.SegmentStatsMonitor` | **EXPERIMENTAL** Reports statistics about segments on Historical services. Available only on Historical services. Not to be used when lazy loading is configured.|
 |`org.apache.druid.server.metrics.QueryCountStatsMonitor`|Reports how many queries have been successful/failed/interrupted.|
 |`org.apache.druid.server.metrics.SubqueryCountStatsMonitor`|Reports how many subqueries have been materialized as rows or bytes and various other statistics related to the subquery execution|
-|`org.apache.druid.server.emitter.HttpEmittingMonitor`|Reports internal metrics of `http` or `parametrized` emitter (see below). Must not be used with another emitter type. See the description of the metrics here: <https://github.com/apache/druid/pull/4973>.|
+|`org.apache.druid.server.emitter.HttpEmittingMonitor`|Reports internal metrics of `http` or `parametrized` emitter (see below). Must not be used with another emitter type. See the description of the metrics here: https://github.com/apache/druid/pull/4973.|
 |`org.apache.druid.server.metrics.TaskCountStatsMonitor`|Reports how many ingestion tasks are currently running/pending/waiting and also the number of successful/failed tasks per emission period.|
 |`org.apache.druid.server.metrics.TaskSlotCountStatsMonitor`|Reports metrics about task slot usage per emission period.|
 |`org.apache.druid.server.metrics.WorkerTaskCountStatsMonitor`|Reports how many ingestion tasks are currently running/pending/waiting, the number of successful/failed tasks, and metrics about task slot usage for the reporting worker, per emission period. Only supported by Middle Manager node types.|
@@ -1192,7 +1192,8 @@ The following table shows the dynamic configuration properties for the Overlord.
 
 The following is an example of an Overlord dynamic config:
 
-<details><summary>Click to view the example</summary>
+<details>
+<summary>Click to view the example</summary>
 
 ```json
 {
@@ -2137,8 +2138,8 @@ The `druid.query.default.context.{query_context_key}` runtime property prefix ap
 
 The precedence chain for query context values is as follows:
 
-hard-coded default value in Druid code <- runtime property not prefixed with `druid.query.default.context`
-<- runtime property prefixed with `druid.query.default.context` <- context parameter in the query
+hard-coded default value in Druid code `<-` runtime property not prefixed with `druid.query.default.context`
+`<-` runtime property prefixed with `druid.query.default.context` `<-` context parameter in the query
 
 Note that not all query context key has a runtime property not prefixed with `druid.query.default.context` that can
 override the hard-coded default value. For example, `maxQueuedBytes` has `druid.broker.http.maxQueuedBytes`

docs/design/extensions-contrib/dropwizard.md

@@ -116,13 +116,6 @@ Latest default metrics mapping can be found [here] (https://github.com/apache/dr
     "type": "timer",
     "timeUnit": "MILLISECONDS"
   },
-  "query/node/backpressure": {
-    "dimensions": [
-      "server"
-    ],
-    "type": "timer",
-    "timeUnit": "MILLISECONDS"
-  },
   "query/segment/time": {
     "dimensions": [],
     "type": "timer",

docs/development/docs-contribute.md

@@ -34,7 +34,7 @@ Druid docs contributors:
 Druid docs contributors can open an issue about documentation, or contribute a change with a pull request (PR).
 
 The open source Druid docs are located here:
-<https://druid.apache.org/docs/latest/design/index.html>
+https://druid.apache.org/docs/latest/design/index.html
 
 If you need to update a Druid doc, locate and update the doc in the Druid repo following the instructions below.
 

docs/development/extensions-core/catalog.md

@@ -52,8 +52,8 @@ A tableSpec defines a table
 | Property     | Type                            | Description                                                               | Required | Default |
 |--------------|---------------------------------|---------------------------------------------------------------------------|----------|---------|
 | `type`       | String                          | the type of table. The only value supported at this time is `datasource`  | yes      | null    |
-| `properties` | Map<String, Object>             | the table's defined properties. see [table properties](#table-properties) | no       | null    |
-| `columns`    | List<[ColumnSpec](#columnspec)> | the table's defined columns                                               | no       | null    |
+| `properties` | Map&lt;String, Object>             | the table's defined properties. see [table properties](#table-properties) | no       | null    |
+| `columns`    | List&lt;[ColumnSpec](#columnspec)> | the table's defined columns                                               | no       | null    |
 
 #### Table Properties
 
@@ -68,7 +68,7 @@ A tableSpec defines a table
 |--------------|---------------------|------------------------------------------------------------------------------------------------------------------------|----------|---------|
 | `name`       | String              | The name of the column                                                                                                 | yes      | null    |
 | `dataType`   | String              | The type of the column. Can be any column data type that is available to Druid. Depends on what extensions are loaded. | no       | null    |
-| `properties` | Map<String, Object> | the column's defined properties. Non properties defined at this time.                                                  | no       | null    |
+| `properties` | Map&lt;String, Object\> | the column's defined properties. Non properties defined at this time.                                                  | no       | null    |
 
 ### APIs
 
@@ -189,7 +189,7 @@ Retrieve a table
 
 ##### URL
 
-`GET` `/druid/coordinator/v1/catalog/schemas/{schema}/tables/{name}
+`GET` `/druid/coordinator/v1/catalog/schemas/{schema}/tables/{name}`
 
 ##### Responses
 
@@ -227,7 +227,7 @@ Retrieve a table
 
 ##### Sample request
 
-The following example shows how to retrieve a table named 'test_table' in schema 'druid'
+The following example shows how to retrieve a table named `test_table` in schema `druid`:
 
 ```shell
 curl "http://ROUTER_IP:ROUTER_PORT/druid/coordinator/v1/catalog/schemas/druid/tables/test_table"
@@ -286,7 +286,7 @@ Delete a table
 
 ##### URL
 
-`DELETE` `/druid/coordinator/v1/catalog/schemas/{schema}/tables/{name}
+`DELETE` `/druid/coordinator/v1/catalog/schemas/{schema}/tables/{name}`
 
 ##### Responses
 
@@ -340,7 +340,7 @@ retrieve list of schema names
 
 ##### URL
 
-`GET` `/druid/coordinator/v1/catalog/schemas
+`GET` `/druid/coordinator/v1/catalog/schemas`
 
 ##### Responses
 
@@ -403,7 +403,7 @@ Retrieve a list of table names in the schema.
 
 ##### URL
 
-`GET` `/druid/coordinator/v1/catalog/schemas/{schema}/table
+`GET` `/druid/coordinator/v1/catalog/schemas/{schema}/table`
 
 ##### Responses