Make safeNumberLongForHash consistent between PPC and other architectures

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: None
    • None
    • Minor Change
    • ALL
    • Query 2019-04-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As noted in SERVER-37183, the hash function used for double values performs an undefined cast when hashing the value 2^63, and the resulting value is different on PPC than on other supported platforms. We should make this hash value consistent across architectures, but before we do that, we need a path for existing PPC installations to rehash any documents with a hashed index key that includes a 2^63 double value.

            Assignee:
            Justin Seyster
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: