Creates a new instance MetadataHandle Used by getOrCreateMetadataHandle in order to create new instances
Returns a map of parameters to be set by the DataSkippingFileFilter on the MetadataHandle when using this MetadataStoreManager.
Returns a map of parameters to be set by the DataSkippingFileFilter on the MetadataHandle when using this MetadataStoreManager. This map can be used to pass specific parameters depending on the type of FileIndex that is being replaced. For example - in parquet.ParquetMetadataStoreManager we can specify that the metadata location should be inferred from the table/default db properties
the table identifier for which the DataSkippingFileFilter will be created
the sparks session
the fileIndex that will be replaced by DataSkippingFileFilter
a map of parameters to be set on the MetadataStore when the DataSkippingFileFilter is created
a map representing relevant MetadataStoreManager parameters
the MetadataStoreManagerType associated with this MetadataStoreManager
A unit function which enables to do setup for the MetadataStoreManager.
A unit function which enables to do setup for the MetadataStoreManager. The setup is called once when the MetadataStoreManager is registered
Map of indexed datasets to their respective md version status and indexes
Clear all active MetadataHandles managed by this MetadataStoreManager
Clears the stats for all active MetadataHandle instances.
Clears the stats for all active MetadataHandle instances. Should be called before each query (or call clearActiveMetadataHandles) to make sure the aggregated stats are cleared
Returns all active MetadataHandles managed by this MetadataStoreManager
Gets the aggregated latest query skipping stats for all active MetadataHandle instances.
Gets the aggregated latest query skipping stats for all active MetadataHandle instances. In order to get reliable results it is assumed that either clearStats or clearActiveMetadataHandles was called before running the query.
This is needed since the way we aggregate the skipping stats is by going over all active
MetadataHandles of the MetadataStoreManager and aggregating their stats.
When running multiple queries there could be a scenario in which the first query used
dataset a
and the second query didn't use it, therefore, when calling aggregatedStats
for the second query the MetadataHandle for dataset a
will be present
as an active MetadataHandle therefore we need its stats to be cleared.
QueryIndexStatsResult instance with the latest query aggregated stats
Gets an existing MetadataHandle or, if there is no existing one, creates a new one.
Gets an existing MetadataHandle or, if there is no existing one, creates a new one.
the sparks session
the table identifier of the dataset for which the MetadataHandle instance is created
a new instance of the MetadataHandle associated with this backend
A trait each MetadataStoreManager should implement