Create separate Ids for DocumentSourceExtensionOptimizable/Expandable

XMLWordPrintableJSON

    • Query Integration
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The static Id currently only exists on DocumentSourceExtension and is shared between the Expandable and Optimizable child classes. This is a slight mistake in the implementation because Expandable stages can be desugared (using the id) and Optimizable stages can be converted to ExtensionStages (using the id).

      However, the inverse is not true for both stages (Expandable cannot be converted to executable and Optimizable cannot be desugared). We should have a separate ids for these DocumentSources to ensure that one cannot perform the tasks of the other.

            Assignee:
            Josh Siegel
            Reporter:
            Josh Siegel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: