Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-104655

Consider updating PlanCacheKey and QuerySettingsHash to use a stable hash implementation

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      As part of upgrading boost in SERVER-70000, the behavior of boost's hashing functionality is changing. boost notably does not guarantee the stability of hash values across versions. As a result, tests that require PlanCacheKey and QuerySettingsHash to be stable will have to be adjusted every time the hashing behavior changes because they use boost to calculate hashes. We should consider arriving at a stable hash implementation (perhaps by implementing it ourselves or vendoring it from elsewhere) and porting PlanCacheKey and QuerySettingsHash (and any other hashes that need to be stable) to use that stable hash implementation. We appear to already have an implementation of murmur hash; it might be sufficient to just use that.

            Assignee:
            Unassigned Unassigned
            Reporter:
            james.bronsted@mongodb.com James Bronsted
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: