...
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 |
|
|
|
|
|
|
|
|
Dedicated Compute (K8S) |
|
|
|
|
|
|
|
|
...
Modify the values of the following properties in the advance properties of semantic model job:
kyvos.process.compute.type=KYVOS_COMPUTE
This property is required only if the Default Compute Cluster Type is External at the application levelkyvos.build.aggregate.type=TABULAR
This property is not required if the semantic model is configured for Kyvos compute-based processing.
Post deployment steps on Azure
Anchor | ||||
---|---|---|---|---|
|
...
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 only if the Default Compute Cluster Type is External at the application levelkyvos.build.aggregate.type=TABULAR
This property is not required if the semantic model is configured for Kyvos compute-based processing.
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.