Interface Planner


  • @Internal
    public interface Planner
    This interface serves two purposes:

    The Planner is execution agnostic. It is up to the TableEnvironment to ensure that if any of the QueryOperation pull any runtime configuration, all those configurations are equivalent. Example: If some of the QueryOperations scan DataStreams, all those DataStreams must come from the same StreamExecutionEnvironment, because the result of translate(List) will strip any execution configuration from the DataStream information.

    All Tables referenced in either Parser.parse(String) or translate(List) should be previously registered in a CatalogManager, which will be provided during instantiation of the Planner.