[SERVER-29907] Dependency tangle within query subsystem Created: 28/Jun/17  Updated: 11/Jan/18  Resolved: 11/Jan/18

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

Type: Bug Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-30815 Migrate library dependencies to LIBDE... Closed
Related
is related to SERVER-29908 Libraries db/s/sharding and db/query/... Closed
is related to SERVER-29909 Libraries db/db_raii and db/s/shardin... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2017-12-18, Platforms 2018-01-01
Participants:

 Description   

There are several direct circular dependencies within the query subsystem. Notably:

  • db/query/query is directly cyclic with db/query/internal_plans. They should probably just be combined.
  • db/exec/exec is directly cyclic with db/query/query.
  • db/exec/exec is indirectly cyclic with db/query/internal_plans, since db/exec/exec depends on db/query/query which depends on db/query/internal_plans, which depends on db/exec/exec.

Note that this tangle extends out in to sharding via a separate direct cyclic dependency between db/query/query and db/s/sharding, which will be separately ticketed.



 Comments   
Comment by Andrew Morrow (Inactive) [ 11/Jan/18 ]

This work was completed under SERVER-30815 in the following commit:

https://github.com/mongodb/mongo/commit/9d1f323a131ba5e3e1af79973ae79910de10a957

Comment by Ian Whalen (Inactive) [ 30/Jun/17 ]

acm is this required for the current dependency project? Or was this just an observation that we should fix this eventually?

Generated at Thu Feb 08 04:22:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.