Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/operations/metrics.md
Original file line number Diff line number Diff line change
Expand Up @@ -350,7 +350,8 @@ These metrics are for the Druid Coordinator and are reset each time the Coordina

### JVM

These metrics are only available if the `JVMMonitor` module is included.
These metrics are only available if the `JvmMonitor` module is included in `druid.monitoring.monitors`.
For more information, see [Enabling Metrics](../configuration/index.md#enabling-metrics).

|Metric|Description|Dimensions|Normal Value|
|------|-----------|----------|------------|
Expand Down
2 changes: 1 addition & 1 deletion docs/querying/lookups.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ In native queries, lookups can be queried with [dimension specs or extraction fu

Query Execution
---------------
When executing an aggregation query involving lookup functions (like the SQL [`LOOKUP` function](sql-scalar.md#string-functions),
When executing an aggregation query involving lookup functions, like the SQL [`LOOKUP` function](sql-scalar.md#string-functions),
Druid can decide to apply them while scanning and aggregating rows, or to apply them after aggregation is complete. It
is more efficient to apply lookups after aggregation is complete, so Druid will do this if it can. Druid decides this
by checking if the lookup is marked as "injective" or not. In general, you should set this property for any lookup that
Expand Down