Investigate Test Coverage for Commands Explicitly Setting apiVersion

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

      A recent help ticket highlighted a specific example where committing a prepared transaction with apiVersion:1 after a failover exposed a testing gap. This points to a broader concern that scenarios involving commands with an explicit apiVersion may not be fully covered by our current tests, especially in failover situations.

            Assignee:
            Unassigned
            Reporter:
            Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: