[SERVER-15301] Remove uses of query options bit vector Created: 18/Sep/14  Updated: 19/Oct/21  Resolved: 19/Oct/21

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

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-15230 Explain find through the find command Closed
Backwards Compatibility: Fully Compatible
Sprint: QE 2021-10-18, QE 2021-11-01
Participants:

 Description   

As of b05a745cd74, the "flags" integer passed as part of an OP_QUERY message is no longer stored as a bit vector, but is parsed to a LiteParsedQuery::Options struct. However, this bit vector is still used in several places (notably, in ClientCursor). As advance work for transitioning from the OP_QUERY wire protocol message to the find command, we should remove any remaining uses of this bit vector.



 Comments   
Comment by Githook User [ 19/Oct/21 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-15301 Remove query options bit vector from CanonicalQuery/ClientCursor
Branch: master
https://github.com/mongodb/mongo/commit/b901d772a793a3aa73acb55c30242e1d000ad0d7

Comment by David Storch [ 01/Oct/21 ]

I think it's worth revisiting this now that OP_QUERY find operations are no longer supported in version 5.1. I'll try to take a look to see if it makes sense to do some cleanup here this sprint.

Generated at Thu Feb 08 03:37:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.