Segment pruning for multi-dim partitioning given query domain

[AmatyaAvadhanula]

Description

Segment pruning for multi-dim partitioning for a given query

DimensionRangeShardSpec#possibleInDomain has been modified to enhance pruning when multi-dim partitioning is used.

Idea

While iterating through each dimension,

1. If query domain doesn't overlap with the set of permissible values in the segment, the segment is pruned.
2. If the overlap happens on a boundary, consider the next dimensions.
3. If there is an overlap within the segment boundaries, the segment cannot be pruned.

Example

Index on (Hour, Minute, Second). Index.size is 3
I)
start = (3, 25, 10)
end = (5, 10, 30)
query domain = {3} * [0, 10] * {10, 20, 30, 40}
EffectiveDomain[:1] == {3} == start[:1]
EffectiveDomain[:2] == {3} * ([0, 10] INTERSECTION [25, INF))
== {} -> PRUNE

II)
start = (3, 25, 10)
end = (5, 15, 30)
query domain = {4} * [0, 10] * {10, 20, 30, 40}
EffectiveDomain[:1] == {4} (!= {} && != start[:1] && != {end[:1]}) -> ACCEPT

III)
start = (3, 25, 10)
end = (5, 15, 30)
query domain = {5} * [0, 10] * {10, 20, 30, 40}
EffectiveDomain[:1] == {5} == end[:1]
EffectiveDomain[:2] == {5} * ([0, 10] INTERSECTION (-INF, 15])
== {5} * [0, 10] (! ={} && != {end[:2]}) -> ACCEPT

IV)
start = (3, 25, 10)
end = (5, 15, 30)
query domain = {5} * [15, 40] * {10, 20, 30, 40}
EffectiveDomain[:1] == {5} == end[:1]
EffectiveDomain[:2] == {5} * ([15, 40] INTERSECTION (-INF, 15])
== {5} * {15} == {end[:2]}
EffectiveDomain[:3] == {5} * {15} * ({10, 20, 30, 40} * (-INF, 30])
== {5} * {15} * {10, 20, 30} != {} -> ACCEPT

V)
start = (3, 25, 10)
end = (5, 15, 30)
query domain = {5} * [15, 40] * {50}
EffectiveDomain[:1] == {5} == end[:1]
EffectiveDomain[:2] == {5} * ([15, 40] INTERSECTION (-INF, 15])
== {5} * {15} == {end[:2]}
EffectiveDomain[:3] == {5} * {15} * ({40} * (-INF, 30])
== {5} * {15} * {}
== {} -> PRUNE

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[lgtm-com]

This pull request introduces 2 alerts when merging b70c0c9 into 6ac4e2d - view on LGTM.com

new alerts:

• 2 for Dereferenced variable may be null

[kfaraz]

Logic looks good to me.

[abhishekagarwal87]

Merged the change since failure is unrelated and code change doesn't affect the phase 2 tests.

[abhishekagarwal87]

Thank you @AmatyaAvadhanula for your first contribution.