Deltas with a triangular or fan shape are called arcuate (arc-like) deltas. The Nile River forms an arcuate delta as it empties into the Mediterranean Sea.
One of the main drivers for data sharing is the knowledge contained within the data. An alternative for sharing data in highly regulated environments can be sharing of models trained on the sensitive data.
Current options are not fit for purpose
Leveraging experiments & model in MLflow, combining it with Delta to leverage Delta Sharing capabilities to enable models exchange
Using Delta Sharing also allow sharing of relevant metadata such as training parameters, model accuracy, artifacts, etc.
The project name takes inspiration from arcuate delta - the wide fan-shaped river delta. We believe that enabling model exchange will have a wide impact on many digitally connected industries.
-
Install the library
pip install arcuate
-
Train model in Databricks (or elsewhere), store it in MLflow
-
Export MLflow experiments & models to a Delta table and add it to a share, using Python APIs
from arcuate import * client = MlflowClient() spark = SparkSession.builder.getOrCreate() # export the experiment experiment_name to table_name, and add it to share_name provider.export_experiments(client, spark, experiment_name, table_name, share_name) # export the model model_name to table_name, and add it to share_name provider.export_models(client, spark, model_name, table_name, share_name)
-
Recipient of this shared table can load it into MLflow seamlessly:
from arcuate import * import delta_sharing client = MlflowClient() spark = SparkSession.builder.getOrCreate() df = delta_sharing.load_as_pandas(delta_sharing_coordinate) # import the shared table as experiment_name recipient.import_experiments(client, df, experiment_name) # or import the model_name recipient.import_models(client, df, model_name)
Please note that all projects in the /databrickslabs github account are provided for your exploration only, and are not formally supported by Databricks with Service Level Agreements (SLAs). They are provided AS-IS and we do not make any guarantees of any kind. Please do not submit a support ticket relating to any issues arising from the use of these projects.
Any issues discovered through the use of this project should be filed as GitHub Issues on the Repo. They will be reviewed as time permits, but there are no formal SLAs for support.
- Vuong Nguyen, Solutions Architect, [email protected]
- Milos Colic, Sr. Solutions Architect, [email protected]