This is an automated email from the ASF dual-hosted git repository.
kfaraz 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 fb8bb5fafd0 docs: Add documentation for fastIntervalSearch config
(#19861)
fb8bb5fafd0 is described below
commit fb8bb5fafd08ea7ec2a5e83704e4c287ef5bede9
Author: pirvtech <[email protected]>
AuthorDate: Thu Sep 10 01:06:07 2026 -0700
docs: Add documentation for fastIntervalSearch config (#19861)
---
docs/configuration/index.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/configuration/index.md b/docs/configuration/index.md
index 14adf3150a3..c5a459368ae 100644
--- a/docs/configuration/index.md
+++ b/docs/configuration/index.md
@@ -1582,6 +1582,12 @@ In `druid.segmentCache.locationSelector.strategy`, one
of `leastBytesUsed`, `rou
Note that if `druid.segmentCache.numLoadingThreads` > 1, multiple threads can
download different segments at the same time. In this case, with the
`leastBytesUsed` strategy or `mostAvailableSize` strategy, Historicals may
select a sub-optimal storage location because each decision is based on a
snapshot of the storage location status of when a segment is requested to
download.
+#### Loading segments
+
+|Property|Description|Default|
+|--------|-----------|-------|
+|`druid.segment.timeline.fastIntervalSearch`|(Experimental) Boolean flag to
enable faster searches of segments in the timeline stored in memory. The
setting when enabled uses an index based on [Interval
tree](https://en.wikipedia.org/wiki/Interval_tree) to organize the timeline
in-memory, for faster loading and searching of segments.|false|
+
#### Historical query configs
##### Concurrent requests
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
