implicitly_retry_on_shard_transition_errors should not rely on hasOwnProperty

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-05-26
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      In at least some cases, the check for whether the command object contains a field is failing due to the use of hasOwnProperty. I tested this locally and replacing hasOwnProperty with in gives the expected results that the property does in fact exist.

              Assignee:
              Allison Easton
              Reporter:
              Allison Easton
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: