For certain index options, $listCatalog output could have inconsistent data type as $listIndexes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • v6.1, v6.0
    • Execution Team 2022-12-26
    • 34
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As an example, if user creates an index and specifies expireAfterSeconds option to be a floating point, like 101.23. The creation would succeed and $listIndexes outputs expireAfterSeconds as an integer 101, since this field is declared to be safeInt in IDL. However $listCatalog would still output expireAfterSeconds as floating point 101.23. This behavior causes issues and confusions to downstream consumers like C2C because the expectation is $listCatalog output is consistent with $listIndexes.

              Assignee:
              Dan Larkin-York
              Reporter:
              Wenbin Zhu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: