Geo 2d index update validation differs between 6.0 and 6.3

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • QE 2023-05-15
    • 120
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This is a bit complex issue, as it depends on a combination of 2 indexes and 2 updates.

      I was able to reproduce the issue using the original fuzzer-generated test and then extracted and minimized the number of indexes and updates.

      The attached script runs without an error on v6.3 and the current master (v7.0), but fails on v6.0 with "geo values must be 'legacy coordinate pairs' for 2d indexes".

      The resmoke command to run the attached script is straightforward: python3 buildscripts/resmoke.py run bf-28454.js

        1. bf-28454.js
          3 kB

            Assignee:
            Alberto Massari
            Reporter:
            Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: