CursorID (long long) printed via LOGV2 can print corrupted value (lower-order bytes altered).

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • Query 2020-11-30
    • 12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Came from investigation on BF-18408. It seems like a platform/hardware specific bug. Not able to reproduce in my local machine but I was able to reproduce on Amazon EC2 instance.

      E.g., cursor id 8388079694692667449, when printing via LOGV2 (or via javascript layer print()) it displays some corrupted value, like, 8388079694692667000.

      P.S: Based on my analysis, the real data isn't corrupted, just the value that gets printed are corrupted (both in c++ and javascript layer).

            Assignee:
            Mindaugas Malinauskas
            Reporter:
            Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: