<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Prakash Hinduja Geneva (Swiss) handle model versioning and rollback in Databricks? in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128197#M4211</link>
    <description>&lt;P&gt;Hi I am Prakash Hinduja Visionary Financial Strategist, born in Amritsar (India) and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;now lives in Geneva&lt;/EM&gt;, Switzerland (Swiss)&lt;/P&gt;&lt;P&gt;I’m working on managing machine learning models in Databricks and wanted to get your insights on best practices for model versioning and rollback. How do you keep track of different versions of your models, and what strategies do you use to revert to a previous version if something goes wrong? Are there built-in tools or workflows within Databricks that you recommend for this purpose? I’d really appreciate any tips, tools, or experiences you can share. Thanks in advance!&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Prakash Hinduja Geneva, Switzerland (Swiss)&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Aug 2025 10:13:45 GMT</pubDate>
    <dc:creator>prakashhinduja1</dc:creator>
    <dc:date>2025-08-12T10:13:45Z</dc:date>
    <item>
      <title>Prakash Hinduja Geneva (Swiss) handle model versioning and rollback in Databricks?</title>
      <link>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128197#M4211</link>
      <description>&lt;P&gt;Hi I am Prakash Hinduja Visionary Financial Strategist, born in Amritsar (India) and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;now lives in Geneva&lt;/EM&gt;, Switzerland (Swiss)&lt;/P&gt;&lt;P&gt;I’m working on managing machine learning models in Databricks and wanted to get your insights on best practices for model versioning and rollback. How do you keep track of different versions of your models, and what strategies do you use to revert to a previous version if something goes wrong? Are there built-in tools or workflows within Databricks that you recommend for this purpose? I’d really appreciate any tips, tools, or experiences you can share. Thanks in advance!&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Prakash Hinduja Geneva, Switzerland (Swiss)&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Aug 2025 10:13:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128197#M4211</guid>
      <dc:creator>prakashhinduja1</dc:creator>
      <dc:date>2025-08-12T10:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Prakash Hinduja Geneva (Swiss) handle model versioning and rollback in Databricks?</title>
      <link>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128276#M4213</link>
      <description>&lt;P&gt;Prakash, you should look at MLFlow, software developed by Databricks and native to our platform.&lt;/P&gt;
&lt;P&gt;I suggest you start by looking here for more information:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/machine-learning/mlops/mlops-workflow" target="_blank"&gt;https://docs.databricks.com/aws/en/machine-learning/mlops/mlops-workflow&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Cheers, Louis.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Aug 2025 19:22:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128276#M4213</guid>
      <dc:creator>Louis_Frolio</dc:creator>
      <dc:date>2025-08-12T19:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Prakash Hinduja Geneva (Swiss) handle model versioning and rollback in Databricks?</title>
      <link>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128656#M4221</link>
      <description>&lt;P&gt;Hi Prakash,&lt;/P&gt;&lt;P&gt;Great question! Databricks provides built-in tools to help with model versioning and rollback, particularly through the Model Registry and Databricks CLI.&lt;/P&gt;&lt;P&gt;To manage model versions programmatically, you can use the Databricks CLI, which includes a set of commands specifically for model version operations. These commands let you:&lt;/P&gt;&lt;P&gt;Register new model versions&lt;/P&gt;&lt;P&gt;Transition model stages (e.g., from "Staging" to "Production")&lt;/P&gt;&lt;P&gt;Delete or restore versions&lt;/P&gt;&lt;P&gt;Retrieve version details&lt;/P&gt;&lt;P&gt;This gives you precise control over model lifecycle management and makes it easier to roll back to a previous version if needed.&lt;/P&gt;&lt;P&gt;You can find the full list of CLI commands for working with model versions here:&lt;BR /&gt;&lt;A href="https://docs.databricks.com/aws/en/dev-tools/cli/reference/model-versions-commands" target="_blank"&gt;https://docs.databricks.com/aws/en/dev-tools/cli/reference/model-versions-commands&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Additionally, within the Databricks UI, the MLflow Model Registry lets you visually manage versions, add comments, track stage transitions, and more.&lt;/P&gt;&lt;P&gt;Let me know if you'd like an example workflow or script using the CLI!&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Wiliam Rosa&lt;/P&gt;</description>
      <pubDate>Sun, 17 Aug 2025 13:40:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/prakash-hinduja-geneva-swiss-handle-model-versioning-and/m-p/128656#M4221</guid>
      <dc:creator>WiliamRosa</dc:creator>
      <dc:date>2025-08-17T13:40:21Z</dc:date>
    </item>
  </channel>
</rss>

