Modal validate does not validate collections that existed at 'atClusterTime' but are no longer in the catalog

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When modal validate is not given a specific collection, it iterates over the collections in the catalog at 'latest'. If validation is run at 'atClusterTime', iterating the catalog at 'latest' can miss some cases. For example, a collection may have been dropped between 'atClusterTime' and 'latest', or it may have been renamed, so that it was collection A at 'atClusterTime' but appears as collection B in the 'latest' catalog.

            Assignee:
            Unassigned
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: