BugZero found this defect 137 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/13/2024
MongoDB Server
No affected releases provided.
8.0.0-rc0
7.0.8
Downstream analysis is finding it hard to identify a single entry, since we flatten out the 'key' object into its components, resulting in something like 50 fields to compare to determine if two entries are the same key (but at different points in time). Adding the hash value will make this easier. Note: there is a question in my mind about whether this should be the SHA256 hash of the materialized 'key' BSON obj, or whether it should be the 'absl::hashOf(const query_stats::Key&)'. I think that it should probably be the former to better ensure that the same 'key' will compare the same across different hosts and possibly different versions of software (which may slightly differ in the absl implementation). This will make it more expensive to compute, so we should be sure to look at performance numbers.
xgen-internal-githook commented on Mon, 11 Mar 2024 18:02:46 +0000: Author: {'name': 'Alyssa Clark', 'email': 'alyssa.clark@mongodb.com', 'username': 'awagenmaker'} Message: SERVER-84530 Add query stats key hash to output of queryStats GitOrigin-RevId: 9b0a00cd412810f6a7523c24ec081c76eac804ed Branch: v7.0 https://github.com/mongodb/mongo/commit/a096bd09bd4fd44c3ad6c8fc4d911529397788a7 xgen-internal-githook commented on Thu, 7 Mar 2024 22:08:10 +0000: Author: {'name': 'Alyssa Wagenmaker', 'email': 'alyssa.clark@mongodb.com', 'username': 'awagenmaker'} Message: SERVER-84530 Add query stats key hash to output of queryStats (#18423) GitOrigin-RevId: 0af4c9296778c347c1962221d8c6309222dc33d0 Branch: master https://github.com/mongodb/mongo/commit/c77a64f6657a3601724d99c133933beb6c97110b