Interface PhysicalOperator

All Superinterfaces:
QueryPlanOperator
All Known Subinterfaces:
BinaryPhysicalOp, BinaryPhysicalOpForLogicalOp, NaryPhysicalOp, NaryPhysicalOpForLogicalOp, NullaryPhysicalOp, NullaryPhysicalOpForLogicalOp, PhysicalOperatorForLogicalOperator, UnaryPhysicalOp, UnaryPhysicalOpForLogicalOp
All Known Implementing Classes:
BaseForPhysicalOpBinaryJoin, BaseForPhysicalOpMultiwayJoin, BaseForPhysicalOpMultiwayLeftJoin, BaseForPhysicalOpSingleInputJoin, PhysicalOpBinaryUnion, PhysicalOpBind, PhysicalOpBindJoinBRTPF, PhysicalOpBindJoinSPARQL, PhysicalOpFilter, PhysicalOpFixedSolMap, PhysicalOpGlobalToLocal, PhysicalOpHashJoin, PhysicalOpHashRJoin, PhysicalOpIndexNestedLoopsJoin, PhysicalOpLocalToGlobal, PhysicalOpLookupJoinViaWrapper, PhysicalOpMultiwayUnion, PhysicalOpNaiveNestedLoopsJoin, PhysicalOpParallelMultiLeftJoin, PhysicalOpRequest, PhysicalOpSymmetricHashJoin, PhysicalOpUnfold

public interface PhysicalOperator extends QueryPlanOperator
This is the top-level interface for all types of physical operators of HeFQUIN, where a physical operator is an element in a (physical) query execution plan and is associated with a concrete algorithm that produces a result (in HeFQUIN, this would be in the form of a sequence of solution mappings) by consuming such results produced by the sub-plans under the current operator.

The createExecOp(boolean, QueryPlanningInfo, ExpectedVariables...) function can be used to obtain an ExecutableOperator that provides an implementation of the algorithm associated with the physical operator in a form that can be plugged directly into the query execution framework of HeFQUIN.