great_expectations.data_context.store.database_store_backend

Module Contents

Classes

DatabaseStoreBackend(credentials, table_name, key_columns, fixed_length_key=True, suppress_store_backend_id=False, manually_initialize_store_backend_id: str = ‘’, store_name=None)

A store backend acts as a key-value store that can accept tuples as keys, to abstract away

great_expectations.data_context.store.database_store_backend.sqlalchemy
great_expectations.data_context.store.database_store_backend.logger
class great_expectations.data_context.store.database_store_backend.DatabaseStoreBackend(credentials, table_name, key_columns, fixed_length_key=True, suppress_store_backend_id=False, manually_initialize_store_backend_id: str = '', store_name=None)

Bases: great_expectations.data_context.store.store_backend.StoreBackend

A store backend acts as a key-value store that can accept tuples as keys, to abstract away reading and writing to a persistence layer.

In general a StoreBackend implementation must provide implementations of:
  • _get

  • _set

  • list_keys

  • _has_key

property store_backend_id(self)

Create a store_backend_id if one does not exist, and return it if it exists Ephemeral store_backend_id for database_store_backend until there is a place to store metadata :returns: store_backend_id which is a UUID(version=4)

_get(self, key)
_set(self, key, value, allow_update=True)
abstract _move(self)
get_url_for_key(self, key)
_convert_engine_and_key_to_url(self, key)
_has_key(self, key)
list_keys(self, prefix=())
remove_key(self, key)