Versions Compared

Version Old Version 1 New Version Current
Changes made by

Sarabjeet Kaur

Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • From Kyvos 2024.11 onwards, you can use the semantic model in a tabular way.

  • When you process a semantic model with no Spark, cuboids are stored at persistent storage. However, a copy of these cuboids is kept at the local storage (local disk).

  • Shared Query Engine: In this mode, the query engine not only performs queries but also handles semantic model processing. This dual role is named SHARED because the same process undertakes both activities.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

From Kyvos 2024.9.1 onwards, if If you use Query Engines as a compute server:

  • For Load Based Scaling: Query Engines will be automatically started when the semantic model is processed.

  • For Schedule based scaling: Query Engines will be start automatically started when the semantic model is processed. However, but if you have enabled scheduledschedule-based scaling, the Query Engines will not auto start automatically. In this casesuch cases, Kyvos recommends switching to Loadload-based scaling.

  • Dedicated Compute: In this mode, the semantic model is processed via dedicated service. In cloud-based deployment, the semantic model is processed using Kubernetes (K8S) cluster-based nodes while in ON PREM environment, models are processed on dedicated nodes.

You can change from an external compute cluster to Kyvos Native for processing semantic models through Kyvos Manager on the Compute Cluster page.

From Kyvos 2024.10 onwards, you can

  • Process semantic model with no-Spark using the Shared Query Engine and dedicated Kubernetes cluster on AWS Managed Services.

  • Resume failed or canceled semantic model process.

  • Run test data Process Test Data job on the semantic model process job.

Supported Platforms

Supported Environments

 

AWS

AZURE

GCP

ON PREM

Supported Native Types

Kyvos Enterprise

Marketplace

Managed Services

Enterprise

Marketplace

Enterprise

Marketplace

 

SHARED QE

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(tick)

Dedicated Compute (K8S)

(tick)

(error)

(tick)

(tick)

(error)

(tick)

(error)

(error)

...

  1. Modify the values of the following properties in the advance properties of semantic model job:

    • kyvos.process.compute.type=KYVOS_COMPUTE

    • kyvos.build.aggregate.type=TABULAR

    Restart Kyvos services

    • Kyvos compute
      This property is required to enable Kyvos compute based processing for the semantic model.

Post deployment steps on Azure
Anchor
postdeployment-Azure
postdeployment-Azure

...

  • To execute the sanity suite for no-spark and Kubernetes (K8S) supported deployments, refer to the Prerequisites for no-spark deployments section.

  • Modify the value of the following semantic model advanced properties on Kyvos Web Portal:

    • kyvos.sqlwarehouse.catalog = ‘Your catalog name’ 

    • kyvos.sqlwarehouse.tempdb = ‘Your Database name’ 

    • kyvos.buildprocess.aggregatecompute.type= TABULAR Kyvos.process.compute.type = Kyvos Compute Kyvos compute
      This property is required to enable Kyvos compute based processing for the semantic model.

  • You can also set subtype to select no-Spark model processing for semantic model via property.
    To do this, navigate to the Kyvos Properties page and update the KYVOS_PROCESS_COMPUTE_SUBTYPE property and restart Kyvos services.

  • For Kyvos Compute (no-Spark) deployments with enhanced security, when creating a Kyvos warehouse connection of a Databricks managed workspace, ensure that the firewall settings on the storage account are disabled.