Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Applies to: (tick) Kyvos Enterprise  (tick) Kyvos Cloud (SaaS on AWS) (tick) Kyvos AWS Marketplace

(tick) Kyvos Azure Marketplace   (tick) Kyvos GCP Marketplace (tick) Kyvos Single Node Installation (Kyvos SNI)


Workflow-based data modeling

As a self-serve tool, Kyvos allows you to define your business case without the need for any coding expertise. To further enhance the user experience, the Quick Data Modeling feature is introduced. It allows you to create data connections quickly, identify your data (available in tables and SQL), and design an semantic model without deep learning of the Kyvos interface. It enables you to build a smart skeleton of your business use case with minimal interaction and bootstrapping work.

Typically, to start your analysis using Kyvos, you need to perform the following five steps.

  1. Connect to data

  2. Create datasets

  3. Define relationships

  4. Design a semantic model

  5. Create visualization/connect to BI tool

With the Quick Data Modeling feature, you can connect to the data source and select the data to register; Kyvos automatically validates your registered data and creates relationships and semantic model design, thereby eliminating the effort and time needed for designing the semantic model.

Let us consider a manufacturing use case for analyzing publicly available SSB data.

  1. On the Kyvos home page, click Quick Data Modeling from the top-right of the home page.

  2. On the displayed wizard, provide an Analysis Name. Kyvos will create all the folders, relationships, and semantic model with this name. In this example, we have named it Kyvos.

  3. Click Start.

  4. On the displayed Create Dataset tab, select your data Connection from the Datasource column.

  5. To modify an existing connection according to your environment, select it from the list and click the Edit link. 

Note

For AWS-based deployments, if your data is available in an S3 bucket other than the one in which Kyvos is installed, select the CustomerDataLake option and click the Edit button to configure a connection to your S3 bucket.

  1. Enter the name of your S3 bucket. You can also use a comma-separated list to add multiple buckets here. 

  2. Click Save.

  1. You can also modify the default Hadoop connection or click a new connection using the Create New Connection link to define a new Snowflake or Redshift data warehouse connection. Refer to the  Working with data connections section to know more.

  2. Select the Input Type from File, Table, or SQL, and proceed as explained below:

Tips

  • Mark at least one fact table. This will help in the auto-creation of relationships and semantic model. You should mark that file as Fact, which you want to use as a fact table in relationships.

  • Mark the primary key and foreign key. This will help in the auto-creation of relationships and semantic model in the next stage. Dimensions/measures will not be created for primary/foreign keys.

  • Hide columns that you do not need in your analysis.

  • Update format if needed.

  1. Choose the Preview Table image-20240226-102409.png icon to see sample data, and click Filter data to refine the data that you want to bring in for your analysis.

  2. Click the Next button. The system validates all your files and tables and displays errors if your data is invalid.

  3. The Define Relationships tab page is displayed with a set of relationships automatically created by the system.
    These relationships are created on the basis of data selected in the previous step and information about master data, fact data, primary key, and foreign key.

  4. If the system does not generate any relationships or to define your custom relationships, you can manually define relationships. For this, click the Add Relationship link.

Tips

  • Create a relationship from fact to dimension by keeping fact on the left side of the relationship.

  • Each table should participate in at least one relationship. In case the table does not have any relations, it will not be used in auto-semantic model creation in the next stage.

  • It is recommended to mark the node that you want to use as fact as a fact table using right-click options.

  1. Click Apply.

  2. The system validates relationships for correctness, and if everything is valid, and generates a semantic model design. The validation status is displayed at the bottom of the screen.

  3. The Design semantic model tab displays the dimensions and measures created by the system.
    By default,  the name of the datasource table from which the first measure is created in the measure group is taken as the  measure group name. However, if you have created a measure group with a custom name, then dragging a measure in it would not impact the name of the measure group.

Note
At any stage in the workflow, if you are not able to complete the workflow because of either the complexity of the use case or if you need some advanced options, which are not available in this interface, you can quit the workflow and can go directly to the standard interface to continue  your work. All the entities created up to the previous steps will be available for users to continue working on the next stage  following the Designer Guide .

For example, if you have created the relationship design, but quit at semantic model design, then your work is done till the relationship design is saved.

  1. You can further modify the design to add dimensions, measures, define dimensions and measure properties, and so on. Refer to Working with Semantic Models to know more.

  2. Click the Next button.

  3. The Review and Process tab shows the entities designed till now.

  4. Here, you can choose any of the following options:
    I want to execute the test process now: Select this option to run the test build and click Process Now.
    You can further choose:

    1. Input Data: Here, you can select the number of records or partitions to be processed in the test build.

    2. Minimal Aggregation: Select the checkbox to minimize aggregations. Aggregates are precalculated summaries that improve query response time. However, semantic model size increases with aggregation.

    3. I want to execute the build later: Select this option if you want to review your design and entities before proceeding with the build. In this case, your design is saved, and you can access the semantic model from Toolbox at any time.

  5. Once you have launched the test build, click View Build Progress to see the build status.
    The system shows the build status in the semantic model designer, as shown in the following figure.

    At the successful completion of your test build, you can start creating visualization and then generate recommendations to further optimize your design.


  • No labels