[SERVER-55608] Allow geo queries on time series views for metadata Created: 30/Mar/21  Updated: 06/Dec/22  Resolved: 02/Sep/21

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jacob Evans Assignee: Backlog - Query Optimization
Resolution: Duplicate Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-55239 Support 2dsphere index on time-series... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

This work is dependant on support for 2d and 2dsphere indexes on time-series collections. This ticket includes support for $geoIntersects, $geoWithin, and the $geoNear stage. Operators $near and $nearSphere and $geoNear currently produces errors when used in any aggregation so we don't need to support them here.

We'd need to change the parsing behavior to specifically allow $geoNear on a time series view. Currently $geoNear must be with a $match at the beginning of the pipeline and is also specifically banned on views (although there is no custom error message).

$geoNear needs custom pushdown. We'd also need a way to divide the stage in twain should the stage be on metadata but a metric be on a data value.

We'd also need to ensure that the meta predicate pushdown code written for SERVER-53484 handles $geoIntersecs and $geoWithin predicates. Tests can be added to pipeline/document_source_internal_unpack_bucket_test/

We should think about the ramifications of this patch. Currently optimization is entirely optional. How should we organize the code for a mandatory rewrite?



 Comments   
Comment by David Percy [ 02/Sep/21 ]

We ended up doing this as part of SERVER-55239.

Generated at Thu Feb 08 05:36:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.