ObsCoreTableManager¶
- class lsst.daf.butler.registry.interfaces.ObsCoreTableManager(*, registry_schema_version: VersionTuple | None = None)¶
Bases:
VersionedExtensionAn interface for populating ObsCore tables(s).
Methods Summary
add_datasets(refs, context)Possibly add datasets to the obscore table.
associate(refs, collection, context)Possibly add datasets to the obscore table.
checkCompatibility(registry_schema_version, ...)Check that schema version defined in registry is compatible with current implementation.
checkNewSchemaVersion(schema_version)Verify that requested schema version can be created by an extension.
clsNewSchemaVersion(schema_version)Class method which returns schema version to use for newly created registry database.
Dump configuration in JSON format.
Return schema version(s) supported by this extension class.
disassociate(refs, collection)Possibly remove datasets from the obscore table.
Return full name of the extension.
initialize(db, context, *, universe, config, ...)Construct an instance of the manager.
Return schema version for newly created registry.
query([columns])Run a SELECT query against obscore table and return result rows.
update_exposure_regions(instrument, region_data)Update existing exposure records with spatial region data.
Methods Documentation
- abstract add_datasets(refs: Iterable[DatasetRef], context: SqlQueryContext) int¶
Possibly add datasets to the obscore table.
This method should be called when new datasets are added to a RUN collection.
- Parameters:
- refs
iterable[DatasetRef] Dataset refs to add. Dataset refs have to be completely expanded. If a record with the same dataset ID is already in obscore table, the dataset is ignored.
- context
SqlQueryContext Context used to execute queries for additional dimension metadata.
- refs
- Returns:
- count
int Actual number of records inserted into obscore table.
- count
Notes
Dataset data types and collection names are checked against configured list of collections and dataset types, non-matching datasets are ignored and not added to the obscore table.
When configuration parameter
collection_typeis not “RUN”, this method should return immediately.Note that there is no matching method to remove datasets from obscore table, we assume that removal happens via foreign key constraint to dataset table with “ON DELETE CASCADE” option.
- abstract associate(refs: Iterable[DatasetRef], collection: CollectionRecord, context: SqlQueryContext) int¶
Possibly add datasets to the obscore table.
This method should be called when existing datasets are associated with a TAGGED collection.
- Parameters:
- refs
iterable[DatasetRef] Dataset refs to add. Dataset refs have to be completely expanded. If a record with the same dataset ID is already in obscore table, the dataset is ignored.
- collection
CollectionRecord Collection record for a TAGGED collection.
- context
SqlQueryContext Context used to execute queries for additional dimension metadata.
- refs
- Returns:
- count
int Actual number of records inserted into obscore table.
- count
Notes
Dataset data types and collection names are checked against configured list of collections and dataset types, non-matching datasets are ignored and not added to the obscore table.
When configuration parameter
collection_typeis not “TAGGED”, this method should return immediately.
- classmethod checkCompatibility(registry_schema_version: VersionTuple, update: bool) None¶
Check that schema version defined in registry is compatible with current implementation.
- Parameters:
- registry_schema_version
VersionTuple Schema version that exists in registry or defined in a configuration for a registry to be created.
- update
bool If True then read-write access is expected.
- registry_schema_version
- Raises:
- IncompatibleVersionError
Raised if schema version is not supported by implementation.
Notes
Default implementation uses
VersionTuple.checkCompatibilityon the versions returned fromcurrentVersionsmethod. Subclasses that support different compatibility model will overwrite this method.
- classmethod checkNewSchemaVersion(schema_version: VersionTuple) None¶
Verify that requested schema version can be created by an extension.
- Parameters:
- schema_version
VersionTuple Schema version that this extension is asked to create.
- schema_version
Notes
This method may be used only occasionally when a specific schema version is given in a regisitry config file. This can be used with an extension that supports multiple schem versions to make it create new schema with a non-default version number. Default implementation compares requested version with one of the version returned from
currentVersions.
- classmethod clsNewSchemaVersion(schema_version: VersionTuple | None) VersionTuple | None¶
Class method which returns schema version to use for newly created registry database.
- Parameters:
- schema_version
VersionTupleorNone Configured schema version or
Noneif default schema version should be created. If notNonethen it is guaranteed to be compatible withcurrentVersions.
- schema_version
- Returns:
- version
VersionTupleorNone Schema version created by this extension.
Noneis returned if an extension does not require its version to be saved or checked.
- version
Notes
Default implementation of this method can work in simple cases. If the extension only supports single schema version than that version is returned. If the extension supports multiple schema versions and
schema_versionis notNonethenschema_versionis returned. If the extension supports multiple schema versions, butschema_versionisNoneit calls_newDefaultSchemaVersionmethod which needs to be reimplemented in a subsclass.
- abstract config_json() str¶
Dump configuration in JSON format.
- Returns:
- json
str Configuration serialized in JSON format.
- json
- abstract classmethod currentVersions() list[lsst.daf.butler.registry.interfaces._versioning.VersionTuple]¶
Return schema version(s) supported by this extension class.
- Returns:
- version
list[VersionTuple] Schema versions for this extension. Empty list is returned if an extension does not require its version to be saved or checked.
- version
- abstract disassociate(refs: Iterable[DatasetRef], collection: CollectionRecord) int¶
Possibly remove datasets from the obscore table.
This method should be called when datasets are disassociated from a TAGGED collection.
- Parameters:
- refs
iterable[DatasetRef] Dataset refs to remove. Dataset refs have to be resolved.
- collection
CollectionRecord Collection record for a TAGGED collection.
- refs
- Returns:
- count
int Actual number of records removed from obscore table.
- count
Notes
Dataset data types and collection names are checked against configured list of collections and dataset types, non-matching datasets are ignored and not added to the obscore table.
When configuration parameter
collection_typeis not “TAGGED”, this method should return immediately.
- classmethod extensionName() str¶
Return full name of the extension.
This name should match the name defined in registry configuration. It is also stored in registry attributes. Default implementation returns full class name.
- Returns:
- name
str Full extension name.
- name
- abstract classmethod initialize(db: Database, context: StaticTablesContext, *, universe: DimensionUniverse, config: Mapping, datasets: Type[DatasetRecordStorageManager], dimensions: DimensionRecordStorageManager, registry_schema_version: VersionTuple | None = None) ObsCoreTableManager¶
Construct an instance of the manager.
- Parameters:
- db
Database Interface to the underlying database engine and namespace.
- context
StaticTablesContext Context object obtained from
Database.declareStaticTables; used to declare any tables that should always be present in a layer implemented with this manager.- universe
DimensionUniverse All dimensions known to the registry.
- config
dict[str,Any] Configuration of the obscore manager.
- datasets
type Type of dataset manager.
- dimensions: `DimensionRecordStorageManager`
Manager for Registry dimensions.
- registry_schema_version
VersionTupleorNone Schema version of this extension as defined in registry.
- db
- Returns:
- manager
ObsCoreTableManager An instance of a concrete
ObsCoreTableManagersubclass.
- manager
- newSchemaVersion() VersionTuple | None¶
Return schema version for newly created registry.
- Returns:
- version
VersionTupleorNone Schema version created by this extension.
Noneis returned if an extension does not require its version to be saved or checked.
- version
Notes
Extension classes that support multiple schema versions need to override
_newDefaultSchemaVersionmethod.
- abstract query(columns: Iterable[str | ColumnElement] | None = None, /, **kwargs: Any) Iterator[CursorResult]¶
Run a SELECT query against obscore table and return result rows.
- Parameters:
- columns
Iterable[str] Columns to return from query. It is a sequence which can include column names or any other column elements (e.g.
sqlalchemy.sql.functions.countfunction).- **kwargs
Restriction on values of individual obscore columns. Key is the column name, value is the required value of the column. Multiple restrictions are ANDed together.
- columns
- Returns:
- result_context
sqlalchemy.engine.CursorResult Context manager that returns the query result object when entered. These results are invalidated when the context is exited.
- result_context
- abstract update_exposure_regions(instrument: str, region_data: Iterable[tuple[int, int, Region]]) int¶
Update existing exposure records with spatial region data.
- Parameters:
- Returns:
- count
int Actual number of records updated.
- count
Notes
This method is needed to update obscore records for raw exposures which are ingested before their corresponding visits are defined. Exposure records added when visit is already defined will get their regions from their matching visits automatically.