[Star Tree] Add date dimension support for range aggregation validation

This change extends the star-tree range aggregation validation to support
DateDimension in addition to NumericDimension. Previously, range aggregations
with star-tree optimization only worked with numeric fields. Now date fields
can also leverage star-tree indexes for range aggregations.

Signed-off-by: Anand Kumar Shaw <anandkrshawheritage@gmail.com>

Author: anandheritage

CHANGELOG.md

@@ -16,6 +16,17 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 - Add index-level-encryption support for snapshots and remote-store ([#20095](https://github.com/opensearch-project/OpenSearch/pull/20095))
 - Adding BackWardCompatibility test for remote publication enabled cluster ([#20221](https://github.com/opensearch-project/OpenSearch/pull/20221))
 - Support for hll field mapper to support cardinality rollups ([#20129](https://github.com/opensearch-project/OpenSearch/pull/20129))
+- Expand fetch phase profiling to support inner hits and top hits aggregation phases  ([##18936](https://github.com/opensearch-project/OpenSearch/pull/18936))
+- Add temporal routing processors for time-based document routing ([#18920](https://github.com/opensearch-project/OpenSearch/issues/18920))
+- Implement Query Rewriting Infrastructure ([#19060](https://github.com/opensearch-project/OpenSearch/pull/19060))
+- The dynamic mapping parameter supports false_allow_templates ([#19065](https://github.com/opensearch-project/OpenSearch/pull/19065))
+- Add a toBuilder method in EngineConfig to support easy modification of configs([#19054](https://github.com/opensearch-project/OpenSearch/pull/19054))
+- Add StoreFactory plugin interface for custom Store implementations([#19091](https://github.com/opensearch-project/OpenSearch/pull/19091))
+- Use S3CrtClient for higher throughput while uploading files to S3 ([#18800](https://github.com/opensearch-project/OpenSearch/pull/18800))
+- Add a dynamic setting to change skip_cache_factor and min_frequency for querycache ([#18351](https://github.com/opensearch-project/OpenSearch/issues/18351))
+- Add overload constructor for Translog to accept Channel Factory as a parameter ([#18918](https://github.com/opensearch-project/OpenSearch/pull/18918))
+- Add subdirectory-aware store module with recovery support ([#19132](https://github.com/opensearch-project/OpenSearch/pull/19132))
+- [Star Tree] Add support for date type dimensions in range aggregation validation ([#20460](https://github.com/opensearch-project/OpenSearch/pull/20460))
 
 ### Changed
 - Handle custom metadata files in subdirectory-store ([#20157](https://github.com/opensearch-project/OpenSearch/pull/20157))

server/src/main/java/org/opensearch/search/startree/StarTreeQueryContext.java

@@ -165,11 +165,13 @@ private static boolean validateRangeAggregationSupport(
         CompositeDataCubeFieldType compositeIndexFieldInfo,
         RangeAggregatorFactory rangeAggregatorFactory
     ) {
-        // Validate request field is part of dimensions & is a numeric field
-        // TODO: Add support for date type ranges
+        // Validate request field is part of dimensions & is a numeric or date field
         return compositeIndexFieldInfo.getDimensions()
             .stream()
-            .anyMatch(dimension -> rangeAggregatorFactory.getField().equals(dimension.getField()) && dimension instanceof NumericDimension);
+            .anyMatch(
+                dimension -> rangeAggregatorFactory.getField().equals(dimension.getField())
+                    && (dimension instanceof NumericDimension || dimension instanceof DateDimension)
+            );
     }
 
     private StarTreeFilter getStarTreeFilter(

server/src/test/java/org/opensearch/search/SearchServiceStarTreeTests.java

@@ -914,11 +914,33 @@ public void testQueryParsingForRangeAggregations() throws IOException {
         sourceBuilder = new SearchSourceBuilder().size(0).query(baseQuery).aggregation(rangeAggregationBuilder);
         assertStarTreeContext(request, sourceBuilder, null, -1);
 
-        // Case 6: Range Aggregation on non-numeric field, should not use star tree
+        // Case 6: Range Aggregation on date field with DateDimension in star-tree, should use star tree
         rangeAggregationBuilder = range("range").field(TIMESTAMP_FIELD).addRange(0, 100).subAggregation(maxAggNoSub);
         baseQuery = new MatchAllQueryBuilder();
         sourceBuilder = new SearchSourceBuilder().size(0).query(baseQuery).aggregation(rangeAggregationBuilder);
-        assertStarTreeContext(request, sourceBuilder, null, -1);
+        assertStarTreeContext(
+            request,
+            sourceBuilder,
+            getStarTreeQueryContext(
+                searchContext,
+                starTreeFieldConfiguration,
+                "startree1",
+                -1,
+                List.of(
+                    new DateDimension(
+                        TIMESTAMP_FIELD,
+                        List.of(new DateTimeUnitAdapter(Rounding.DateTimeUnit.MONTH_OF_YEAR)),
+                        DateFieldMapper.Resolution.MILLISECONDS
+                    ),
+                    new OrdinalDimension(KEYWORD_FIELD)
+                ),
+                List.of(new Metric(STATUS, List.of(MetricStat.SUM, MetricStat.MAX))),
+                baseQuery,
+                sourceBuilder,
+                true
+            ),
+            -1
+        );
 
         // Case 7: Valid range aggregation and valid metric aggregation, should use star tree & cache
         rangeAggregationBuilder = range("range").field(NUMERIC_FIELD).addRange(0, 100).subAggregation(maxAggNoSub);