@@ -190,7 +190,7 @@ following list provides a non-exhaustive overview of some of the major benefits.
190190 within a range; find previous executions in a context with the same inputs.
191191
192192See the
193- [ MLMD tutorial] ( https://www. tensorflow.org /tfx/tutorials/mlmd/mlmd_tutorial ) for
193+ [ MLMD tutorial] ( https://tensorflow.github.io /tfx/tutorials/mlmd/mlmd_tutorial/ ) for
194194an example that shows you how to use the MLMD API and the metadata store to
195195retrieve lineage information.
196196
@@ -484,10 +484,11 @@ the steps together within a single transaction, and the transaction is
484484rolled-back when an error occurs. The migration script is provided together with
485485any schema-change commit and verified through testing.
486486
487- Note: The migration DDLs in MySQL are not transactional. When using MySQL, there
488- should only be a single connection with the upgrade migration enabled to use the
489- old database. Take a backup of the database before upgrading to prevent
490- potential data losses.
487+ !!! Note
488+ The migration DDLs in MySQL are not transactional. When using MySQL, there
489+ should only be a single connection with the upgrade migration enabled to use the
490+ old database. Take a backup of the database before upgrading to prevent
491+ potential data losses.
491492
492493### Downgrade the database schema
493494
@@ -509,11 +510,12 @@ metadata_store.downgrade_schema(connection_config,
509510 downgrade_to_schema_version = 0 )
510511```
511512
512- Note: When downgrading, MLMD prevents data loss as much as possible. However,
513- newer schema versions might be inherently more expressive and hence a downgrade
514- can introduce data loss. When using backends that do not support DDL
515- transactions (e.g., MySQL), the database should be backed up before downgrading
516- and the downgrade script should be the only MLMD connection to the database.
513+ !!! Note
514+ When downgrading, MLMD prevents data loss as much as possible. However,
515+ newer schema versions might be inherently more expressive and hence a downgrade
516+ can introduce data loss. When using backends that do not support DDL
517+ transactions (e.g., MySQL), the database should be backed up before downgrading
518+ and the downgrade script should be the only MLMD connection to the database.
517519
518520The list of ` schema_version ` used in MLMD releases are:
519521
@@ -555,7 +557,7 @@ ml-metadata (MLMD) | schema_version
555557
556558The MLMD library has a high-level API that you can readily use with your ML
557559pipelines. See the
558- [ MLMD API documentation] ( https://www.tensorflow.org/tfx/ml_metadata/api_docs/python/ mlmd)
560+ [ MLMD API documentation] ( api/ mlmd/ )
559561for more details.
560562
561563Check out
@@ -564,5 +566,5 @@ to learn how to use MLMD declarative nodes filtering capabilities on properties
564566and 1-hop neighborhood nodes.
565567
566568Also check out the
567- [ MLMD tutorial] ( https://www. tensorflow.org /tfx/tutorials/mlmd/mlmd_tutorial ) to
569+ [ MLMD tutorial] ( https://tensorflow.github.io /tfx/tutorials/mlmd/mlmd_tutorial/ ) to
568570learn how to use MLMD to trace the lineage of your pipeline components.
0 commit comments