Engine¶
- class lsst.daf.relation.iteration.Engine(*, name: str = 'iteration', functions: dict[str, _F] = <factory>, relation_name_counter: int = 0)¶
- Bases: - GenericConcreteEngine[- Callable[…,- Any]]- A concrete engine that treats relations as iterables with - Mappingrows.- See the - iterationmodule documentation for details.- Attributes Summary - Name of the engine; primarily used for display purposes ( - str).- An integer counter used to generate relation names ( - int).- Methods Summary - append_binary(operation, lhs, rhs)- Hook for maintaining the engine's - conforminvariants through- BinaryOperation.apply.- append_unary(operation, target)- Hook for maintaining the engine's - conforminvariants through- UnaryOperation.apply.- apply_custom_unary_operation(operation, target)- Convert a custom - UnaryOperationto a- RowIterable.- backtrack_unary(operation, tree, preferred)- Attempt to insert a unary operation in another engine upstream of this one by via operation commutators. - conform(relation)- Ensure a relation tree satisfies this engine's invariants. - convert_column_container(expression)- Convert a - ColumnContainerto a Python callable.- convert_column_expression(expression)- Convert a - ColumnExpressionto a Python callable.- convert_predicate(predicate)- Convert a - Predicateto a Python callable.- execute(relation)- Execute a native iteration relation, returning a Python iterable. - get_doomed_payload(columns)- Return a - payloadfor a leaf relation that has no rows.- get_function(name)- Return the named column expression function. - Return a - payloadfor a leaf relation that is the- join identity.- get_relation_name([prefix])- Return a name suitable for a new relation in this engine. - make_doomed_relation(columns, messages[, name])- Construct a leaf relation with no rows and one or more messages explaining why. - make_join_identity_relation([name])- Construct a leaf relation with no columns and exactly one row. - make_leaf(columns, payload, *[, name, ...])- Create a nontrivial leaf relation in this engine. - materialize(target[, name, name_prefix])- Mark that a target relation's payload should be cached. - transfer(target[, payload])- Mark that a relation's payload should be transferred from some other engine to this one. - Attributes Documentation - Methods Documentation - append_binary(operation: BinaryOperation, lhs: Relation, rhs: Relation) Relation¶
- Hook for maintaining the engine’s - conforminvariants through- BinaryOperation.apply.- This method should only be called by - BinaryOperation.applyand the engine’s own methods and helper classes. External code should call- BinaryOperation.applyor a- Relationfactory method instead.- Parameters:
- operationBinaryOperation
- Operation to apply; should already be filtered through - BinaryOperation._begin_apply.
- lhsRelation
- One relation to apply the operation to directly. 
- rhsRelation
- The other relation to apply the operation to directly. 
 
- operation
- Returns:
- relationRelation
- Relation that includes the given operation acting on - lhsand- rhs, or a simplified equivalent.
 
- relation
 - Notes - Implementations should delegate back to - UnaryOperation._finish_applyto actually create a- UnaryOperationRelationand perform final simplification and checks. This is all the default implementation does.
 - append_unary(operation: UnaryOperation, target: Relation) Relation¶
- Hook for maintaining the engine’s - conforminvariants through- UnaryOperation.apply.- This method should only be called by - UnaryOperation.applyand the engine’s own methods and helper classes. External code should call- UnaryOperation.applyor a- Relationfactory method instead.- Parameters:
- operationUnaryOperation
- Operation to apply; should already be filtered through - UnaryOperation._begin_apply.
- targetRelation
- Relation to apply the operation to directly. 
 
- operation
- Returns:
- relationRelation
- Relation that includes the given operation acting on - target, or a simplified equivalent.
 
- relation
 - Notes - Implementations should delegate back to - UnaryOperation._finish_applyto actually create a- UnaryOperationRelationand perform final simplification and checks. This is all the default implementation does.
 - apply_custom_unary_operation(operation: UnaryOperation, target: Relation) RowIterable¶
- Convert a custom - UnaryOperationto a- RowIterable.- This method must be implemented in a subclass engine in order to support any custom - UnaryOperation.- Parameters:
- operationUnaryOperation
- Operation to apply. Guaranteed to be a - Marker,- Reordering, or- RowFiltersubclass.
- targetRelation
- Target of the unary operation. Typically this will be passed to - executeand the result used to construct a new- RowIterable.
 
- operation
- Returns:
- rowsRowIterable
- Iterable over rows, with each row a mapping keyed by - ColumnTag.
 
- rows
 
 - backtrack_unary(operation: UnaryOperation, tree: Relation, preferred: Engine) tuple[lsst.daf.relation._relation.Relation, bool, tuple[str, ...]]¶
- Attempt to insert a unary operation in another engine upstream of this one by via operation commutators. - Parameters:
- operationUnaryOperation
- Unary operation to apply. 
- treeRelation
- Relation tree the operation logically acts on; any upstream insertion of the given operation should be equivalent to applying it to the root of this tree. Caller guarantees that - tree.engine == self.
- preferredEngine
- Engine in which the operation or its commuted equivalent should be performed. 
 
- operation
- Returns:
- new_treeRelation
- Possibly-updated relation tree. 
- donebool
- If - True, the operation has been fully inserted upstream in the preferred engine. If- False, either- treewas returned unmodified or only a part of the operation (e.g. a projection whose columns are superset of the given projection’s) was inserted upstream.
- messagesSequence[str]
- Messages explaining why backtracking insertion was unsuccessful or incomplete. Should be sentences with no trailing - .and no capitalization; they will be joined with semicolons.
 
- new_tree
 
 - conform(relation: Relation) Relation¶
- Ensure a relation tree satisfies this engine’s invariants. - This can include reordering operations (in a way consistent with their commutators) and/or inserting - MarkerRelationnodes.- Parameters:
- relationRelation
- Original relation tree. 
 
- relation
- Returns:
- conformedRelation
- Relation tree that satisfies this engine’s invariants. 
 
- conformed
 - Notes - The default implementation returns the given relation. Engines with a non-trivial - conformimplementation should always call it on any relations they are passed, as algorithms that process the relation tree are not guaranteed to maintain those invariants themselves. It is recommended to use a custom- MarkerRelationto indicate trees that satisfy invariants, allowing the corresponding- conformimplementation to short-circuit quickly.
 - convert_column_container(expression: ColumnContainer) Callable[[Mapping[ColumnTag, Any]], Container]¶
- Convert a - ColumnContainerto a Python callable.- Parameters:
- expressionColumnContainer
- Expression to convert. 
 
- expression
- Returns:
- callable
- Callable that takes a single - Mappingargument (with- ColumnTagkeys and regular Python values, representing a row in a relation), returning the evaluated expression as- collections.abc.Containerinstance.
 
 
 - convert_column_expression(expression: ColumnExpression) Callable[[Mapping[ColumnTag, Any]], Any]¶
- Convert a - ColumnExpressionto a Python callable.- Parameters:
- expressionColumnExpression
- Expression to convert. 
 
- expression
- Returns:
 
 - convert_predicate(predicate: Predicate) Callable[[Mapping[ColumnTag, Any]], bool]¶
- Convert a - Predicateto a Python callable.
 - execute(relation: Relation) RowIterable¶
- Execute a native iteration relation, returning a Python iterable. - Parameters:
- relationRelation
- Relation to execute. 
 
- relation
- Returns:
- rowsRowIterable
- Iterable over rows, with each row a mapping keyed by - ColumnTag.
 
- rows
 - Notes - This method does not in general iterate over the relation’s rows; while some operations like - Sortand- Deduplicationdo require processing all rows up front (which will happen during a call to- execute), most return lazy iterables that do little or nothing until actually iterated over.- This method requires all relations in the tree to have the same engine ( - self). Use the- Processorclass to handle trees with multiple engines.
 - get_doomed_payload(columns: Set[ColumnTag]) RowIterable¶
- Return a - payloadfor a leaf relation that has no rows.- Parameters:
- columnsSet[ColumnTag]
- The columns the relation should have. 
 
- columns
- Returns:
- payload
- The engine-specific content for this relation. 
 
 
 - get_function(name: str) _F | None¶
- Return the named column expression function. - Parameters:
- namestr
- Name of the function, from - ColumnFunction.nameor- PredicateFunction.name
 
- name
- Returns:
- function
- Engine-specific callable, or - Noneif no match was found.
 
 - Notes - This implementation first looks for a symbol with this name in the built-in - operatormodule, to handle the common case (shared by both the- iterationand- sqlengines) where these functions are appropriate for the engine due to operator overloading. When this fails, the name is looked up in the- functionsattribute.
 - get_join_identity_payload() RowIterable¶
- Return a - payloadfor a leaf relation that is the- join identity.- Returns:
- payload
- The engine-specific content for this relation. 
 
 
 - get_relation_name(prefix: str = 'leaf') str¶
- Return a name suitable for a new relation in this engine. - Parameters:
- prefixstr, optional
- Prefix to include in the returned name. 
 
- prefix
- Returns:
- namestr
- Name for the relation; guaranteed to be unique over all of the relations in this engine. 
 
- name
 - Notes - This implementation combines the given prefix with both the current - relation_name_countervalue and a random hexadecimal suffix.
 - make_doomed_relation(columns: Set[ColumnTag], messages: Sequence[str], name: str = '0') Relation¶
- Construct a leaf relation with no rows and one or more messages explaining why. - Parameters:
- Returns:
- relationRelation
- Doomed relation. 
 
- relation
 - Notes - This is simplify a convenience method that delegates to - LeafRelation.make_doomed. Derived engines with a nontrivial- conformshould override this method to conform the return value.
 - make_join_identity_relation(name: str = 'I') Relation¶
- Construct a leaf relation with no columns and exactly one row. 
 - make_leaf(columns: Set[ColumnTag], payload: MaterializedRowIterable, *, name: str = '', messages: Sequence[str] = (), name_prefix: str = 'leaf', parameters: Any = None) LeafRelation¶
- Create a nontrivial leaf relation in this engine. - This is a convenience method that simply forwards all arguments to the - LeafRelationconstructor; see that class for details.
 - materialize(target: Relation, name: str | None = None, name_prefix: str = 'materialization_') Relation¶
- Mark that a target relation’s payload should be cached. - Parameters:
- targetRelation
- Relation to mark. 
- namestr, optional
- Name to use for the cached payload within the engine. 
- name_prefixstr, optional
- Prefix to pass to - get_relation_name; ignored if- nameis provided.
 
- target
- Returns:
- relationRelation
- New relation that marks its upstream tree for caching, unless the materialization was simplified away. 
 
- relation
 - See also - Processor.materialize
 - Notes - The base class implementation calls - Materialization.simplifyto avoid materializations of leaf relations or other materializations. Override implementations should generally do the same.
 - transfer(target: Relation, payload: Any | None = None) Relation¶
- Mark that a relation’s payload should be transferred from some other engine to this one. - Parameters:
- targetRelation
- Relation to transfer. If - target.engine == self, this relation will be returned directly and no transfer will be performed. Back-to-back transfers from one engine to another and back again are also simplified away (via a call to- Transfer.simplify). Sequences of transfers involving more than two engines are not simplified.
- payload, optional
- Destination-engine-specific content for the relation to attach to the transfer. Most - Transferrelations do not have a payload; their ability to do so is mostly to support the special relation trees returned by the- Processorclass.
 
- Returns:
- relationRelation
- New relation that marks its upstream tree to be transferred to a new engine. 
 
- relation
 - See also - Processor.transfer
 - Notes - The default implementation calls - conformon the target relation using the target relation’s engine (i.e. not- self). All override implementations should do this as well.