Skip to main content

Prophecy 4.1.1 Extended Maintenance (EM) Release

June 19, 2025

Prophecy 4.1.1.0 is an extended maintenance release. Learn more in Prophecy versions support.

Prophecy for Analysts​

Features​

The following features and enhancements are available in this release.

  • Databricks connections in Prophecy fabrics now accept service principal credentials for OAuth. Now you can deploy scheduled pipelines using the service principal credentials. To learn more, visit the Databricks connection documentation.

  • The Run History tab in the Observability interface now displays the Run Type and Run ID for each historical pipeline run.

  • We've added the ability to reindex your SQL warehouse for the knowledge graph. This ensures that Prophecy's AI agent has the latest information about your datasets (Added in 4.1.1.2).

  • The new Power BI connection and PowerBIWrite gem allow you to you publish pipeline results directly to Power BI tables (Added in 4.1.1.5).

Prophecy for Engineers​

Features​

The following features and enhancements are available in this release.

  • You can now fetch and reference the hidden _metadata column from input files in Databricks. Spark projects only.

  • For target models running on BigQuery SQL fabrics, you can now configure overwrite modes to partition by a specific column and appropriate partitions (Added in 4.1.1.1).

Fixes​

The following fix is available in this release.

  • Spark project deployment is no longer blocked when you are missing service principal on an unrelated fabric using Databricks OAuth (Fixed in 4.1.1.1).

Prophecy Library versions​

The following are the newest available Prophecy Library versions in this release.

  • ProphecyLibsPython 1.9.49

  • ProphecyLibsScala 8.10.1

Global Updates​

  • We updated tornado and jupyter_core in the Python sandbox to address CVE-2025-47287 and CVE-2025-30167, respectively.

  • We updated helm to version 3.18.4 to address CVE-2025-53547.

  • SparkEdge could not authenticate with Artifactory when secrets were stored as files because we required the master password to be available as an environment variable. We now support mounting the encrypted master password as a file via a Kubernetes secret. This fix applies to self-hosted deployments only.