Get rid of ShardFilterer

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The  ShardFilterer utility serves both as a "range preserver" and as a façade to the underlying orphan filter provided by sharding. It also has some dubious methods, like clone.

      With the introduction of the ShardRole API and its integration in the PlanExecutor infrastructure, queries no longer need to explicitly declare range preservation and also they have access to the collection description/filter and data, so this class is no longer necessary.

            Assignee:
            Unassigned
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: