Drops all of the metadata associated with the given index
Finalize metadata creation in the metadatastore (implementation specific)
Returns a set of all indexed files (async)
Maximum number of objects to delete in one chunk
Returns index statistics
returns the sequence of indexes that exist in the metadatastore for the tableIdentifier
returns the version status of the metadata.
returns the version status of the metadata. we do not have a strict requirement for the metadatastore to use metadata from a version different than its current version for filtering / refresh but we do expect it to be able to tell the version status, and whether or not it can be upgraded to comply with the current version.
the version of the metadata
Returns the required file ids for the given query (async)
Returns the required file ids for the given query (async)
the query to be used in order to get the relevant files (this query is of type Any and it is the responsibility of the metadatastore implementation to cast it to as instance which matches the translation for this MetaDataStore)
the set of fileids required for this query
Maximum number of objects to index in one chunk
Returns true if an index exists for the tableIdentifier
Returns true if an index exists for the tableIdentifier
true if the an index exists for the tableIdentifier
returns whether or not the metadata can be upgraded to comply with the current version
returns whether or not the metadata can be upgraded to comply with the current version
true if the metadata can be upgraded, false otherwise
Refreshes the MetadataHandle by re-syncing with the metadatastore (implementation specific)
Removes the metadata for a sequence of files.
Removes the metadata for a sequence of files. This method may assume that the Metadta version status is MetadataVersionStatus.CURRENT
a sequence of files for which the metadata will be removed
Set metadataStore specific parameters such as user, password, host Note: the implementation should not count on the Map not changing during the run therefore, it needs to save its parameters locally
Set metadataStore specific parameters such as user, password, host Note: the implementation should not count on the Map not changing during the run therefore, it needs to save its parameters locally
a map of parameters (each metadata store expects certain input)
Upgrades the metadata to comply with the current version
Upgrades the metadata to comply with the current version
- the indexes stored in the metadataStore.
Uploads the metadata to the metadatastore This method may assume that the metadata version status is MetadataVersionStatus.CURRENT
Uploads the metadata to the metadatastore This method may assume that the metadata version status is MetadataVersionStatus.CURRENT
RDD that contains for each file a list of abstract metaData types to be uploaded
a sequence of indexes that created the metadata
indicates whether the operation is a refresh operation
Cleans the MetadataHandle instance (implementation specific)
Clears the latest stats
Initialize metadata for a dataset in the metadatastore (implementation specific)
Initialize metadata for a dataset in the metadatastore (implementation specific)
a sequence of metadata indexes
Returns whether or not this MetadataHandle supports encryption
Returns whether or not this MetadataHandle supports encryption
true if the MetadataHandle supports encryption
Updates the MetadataHandle stats with the given query stats called from the dataSkippingFileIndex rule in the catalyst to update the stats during the query tun time
Updates the MetadataHandle stats with the given query stats called from the dataSkippingFileIndex rule in the catalyst to update the stats during the query tun time
the updated stats
a trait each MetadataHandle should implement note that the tableIdentifier is not in the signature since it is likely that it will be passed in the constructor.