Do not use KeyString for metadata comparisons in BucketCatalog

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Execution Team 2021-03-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the BucketCatalog uses KeyString to facilitate metadata comparisons in the BucketCatalog. This lets numbers of different types compare equal when they shouldn't for this purpose. Instead, we should simply store a field-sorted object and then do a binary comparison over the object.

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

              Created:
              Updated:
              Resolved: