Running open-Jev in SQL on Databricks

Imported from official source

  • Run models like SemIf-OpenJev directly on governed Databricks data using serverless GPUs and managed Model Serving.
  • Query custom model endpoints from SQL or Lakeflow jobs with ai_query, returning structured decisions and probability scores at scale.
  • Get started with an importable notebook that deploys the model in a few steps, then adapt it to your own data, decision criteria, and use cases.
  • Over the weekend, “System One” decision models such as Jev have launched, which are a growing class of foundation models that are able to produce well-calibrated decisions from a discrete set of options. These models are usually extremely fast and also cheap, allowing a broad range of applications on large data. Potential use cases range from analyzing customer support transcripts, to applying complex decisions at scale across your data.

    The open source community has also been busy launching open weight versions of these decision models, from Smelf-open-jev, to Laya, to Kev. But the power of these models are only unlocked when they can touch large amounts of data. Today we are excited to share how you can serve open weight decision models on Databricks, and run them directly on your governed data. You can even access these models directly from your SQL console or production jobs in Lakeflow via ai_query. Moreover, products like AI Runtime enable you to customize or post-train these models to tailor them to your specific enterprise context.

    In this post, we’ll show how you can use such a model, SemIf-OpenJev, directly in Databricks, to classify hotel reviews as good or bad.

    We’ve packaged the workflow into an importable Databricks Notebook.

    The notebook uses Databricks AI Runtime to provide serverless, on-demand GPU compute without requiring you to set up or manage GPU infrastructure.

  • Downloads the SemIf-OpenJev model files.
  • Logs and registers the model using Express Deployments.
  • Creates a GPU Model Serving endpoint automatically.
  • This is an extract. The publication continues at the source.

    Read the original at the source: https://www.databricks.com/blog/running-open-jev-sql-databricks

    Officially imported this from Databricks’s own source and shows an extract. If you work there, claiming the profile and verifying the domain lets you choose to show the full text here.

    Provenance

    Organization
    Databricks — imported from official source
    Official source
    https://www.databricks.com/feed RSS
    Imported
    September 24, 2026 20:00
    Versions
    1 recorded
    Identity
    https://www.databricks.com/blog/running-open-jev-sql-databricks

    Officially records where a publication came from, not whether it is true. Imported records are reproduced from an organization's own official source.