1. Home
  2. Latest Release Docs
  3. Guides
  4. Concepts
  5. Tools
  6. References
    1. Apache Spark
    2. Built-in Functions
    3. Incorta Component SDK
    4. Incorta Connector SDK
    5. Connectors
    6. Data Studio
      1. Enabling the Data Studio
      2. Aggregation Recipe
      3. Change Type Recipe
      4. Data Quality Recipe
      5. Filter Recipe
      6. Formula Recipe
      7. Fuzzy Join Recipe
      8. Join Recipe
      9. LLM Recipe
      10. Python Recipe
      11. Rename Recipe
      12. Sample Recipe
      13. Save MV Recipee
      14. Select Recipe
      15. Sort Recipe
      16. Split Recipe
      17. SQL Recipe
      18. Union Recipe
      19. Unpivot Recipe
    7. Public API
    8. Security
    9. SQL Interface
    10. Visualizations
    11. Other
  7. Integrations
  8. Data applications
  9. Release Notes
  10. Incorta Premium

References → Save MV Recipe

The Save MV recipe is the final step of any data flow. The save MV recipe will take all the upstream logic of the data flow and deploy it into a physical schema as Materialized View (MV) written in PySpark.

Important: Incremental Mode

For the releases of 2024.1.5, 2024.7.0, 2024.7.1, activating the Incremental Mode toggle on this Recipe will result in failure to deploy the Dataflow to publish to the target Schema. Turn off Incremental Mode, deploy, then edit the incremental logic in the Physical Schema.

This issue has been resolved in 2024.7.2.

Configuration

ConfigurationDescription
InputSelect a previously constructed recipe as an input
SchemaSelect a schema to save the data flow logic to
MV NameGive a name to the MV to be created

Previewing the Code

To review the code generated in the data flow, select the desired recipe and select Preview Code

Deploying the Data Flow

Now that you have saved the Save MV recipe, you have two options for deployment.

  1. With the Save MV recipe highlighted, select deploy from the data studio banner header.

  2. With the Save MV recipe highlighted, select deploy from the toolbar

Note

Deploying an MV will overwrite any existing MV with the same name in the same physical schema.