mlmd.downgrade_schema
Stay organized with collections
Save and categorize content based on your preferences.
Downgrades the db specified in the connection config to a schema version.
mlmd.downgrade_schema(
config: proto.ConnectionConfig, downgrade_to_schema_version: int
) -> None
If downgrade_to_schema_version
is greater or equals to zero and less than
the current library's schema version, it runs a downgrade transaction to
revert the db schema and migrate the data. The update is transactional, and
any failure will cause a full rollback of the downgrade. Once the downgrade
is done, the user needs to use the older version of the library to connect to
the database.
Args |
config
|
a proto.ConnectionConfig having the connection params.
|
downgrade_to_schema_version
|
downgrades the given database to a specific
version. For v0.13.2 release, the schema_version is 0. For 0.14.0 and
0.15.0 release, the schema_version is 4. More details are described in
g3doc/get_start#upgrade_mlmd_library
|
Raises |
errors.InvalidArgumentError
|
if the downgrade_to_schema_version is not
given or it is negative or greater than the library version.
|
RuntimeError
|
if the downgrade is not finished, return detailed error.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-04-18 UTC.
[null,null,["Last updated 2025-04-18 UTC."],[],[],null,["# mlmd.downgrade_schema\n\n\u003cbr /\u003e\n\n|--------------------------------------------------------------------------------------------------------------------------------------|\n| [View source on GitHub](https://github.com/google/ml-metadata/blob/v1.17.0/ml_metadata/metadata_store/metadata_store.py#L1987-L2027) |\n\nDowngrades the db specified in the connection config to a schema version. \n\n mlmd.downgrade_schema(\n config: proto.ConnectionConfig, downgrade_to_schema_version: int\n ) -\u003e None\n\nIf `downgrade_to_schema_version` is greater or equals to zero and less than\nthe current library's schema version, it runs a downgrade transaction to\nrevert the db schema and migrate the data. The update is transactional, and\nany failure will cause a full rollback of the downgrade. Once the downgrade\nis done, the user needs to use the older version of the library to connect to\nthe database.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| Args ---- ||\n|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `config` | a `proto.ConnectionConfig` having the connection params. |\n| `downgrade_to_schema_version` | downgrades the given database to a specific version. For v0.13.2 release, the schema_version is 0. For 0.14.0 and 0.15.0 release, the schema_version is 4. More details are described in g3doc/get_start#upgrade_mlmd_library |\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| Raises ------ ||\n|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|\n| [`errors.InvalidArgumentError`](https://www.tensorflow.org/api_docs/python/tf/errors/InvalidArgumentError) | if the `downgrade_to_schema_version` is not given or it is negative or greater than the library version. |\n| `RuntimeError` | if the downgrade is not finished, return detailed error. |\n\n\u003cbr /\u003e"]]