…er a trial period
The showDiskLoc() shell helper is now an alias for showRecordId(). The server still accepts $showDiskLoc for OP_QUERY style find operations. For find command, the showDiskLoc argument has been renamed to showRecordId. Also renames the $diskLoc field returned in the resulting documents to $recordId. Unlike $diskLoc, the $recordId field reports a single 64 bit integer rather than separately reporting the high-order 32 bits and low-order 32 bits, which have MMAPv1-specific meaning of file and offset.
The exhaust option is supported only for OP_QUERY style find.
…nges before a ClientCursor is established
Since WT does not issue invalidations, docs will not be removed from the hash table when they are updated.
Introduces getExecutorFind(), a unified way to retrieve a PlanExecutor for find operations.
This was used for filtering orphaned chunks. However, it no longer needs to be stashed in the ClientCursor, as it now lives in the ShardFilterStage.
…pec changes Also updates the shell to construct the find command according to the new spec. This means that explain with special options (e.g. snapshot()) will not be compatible when mixing 3.2 shell / 3.0 server or 3.0 shell / 3.2 server. Explain of find with standard options like filter, query, projection, sort, and hint will be both backwards and forwards compatible.
…o trigger a logOp() rollback
…upsert: true, new: false case
… used by DensityEstimator
…on to use tighter index bounds