ReOrc docs
Get ReOrc
English
English
  • About ReOrc
  • Set up and deployment
    • Set up organization
    • Install ReOrc agent
  • Getting started
    • 1. Set up a connection
      • BigQuery setup
    • 2. Create a project
    • 3. Create data models
    • 4. Build models in console
    • 5. Set up a pipeline
  • Connections
    • Destinations
      • Google Service Account
    • Integrations
      • Slack
  • Data modeling
    • Overview
    • Sources
    • Models
      • Model schema
      • Model configurations
    • Jinja templating
      • Variables
      • Macros
    • Materialization
    • Data lineage
    • Data tests
      • Built-in generic tests
      • Custom generic tests
      • Singular tests
  • Semantic modeling
    • Overview
    • Data Modelling vs Semantic Layer
    • Cube
      • Custom Dimension
      • Custom Measure
        • Aggregation Function
        • SQL functions and operators
        • Calculating Period-over-Period Changes
      • Relationship
    • View
      • Primary Dimension
      • Add Shared Fields
    • Shared Fields
    • Integration
      • Guandata Integration
      • Looker Studio
  • Pipeline
    • Overview
    • Modeling pipeline
    • Advanced pipeline
    • Job
  • Health tracking
    • Pipeline health
    • Data quality
  • Data governance
    • Data protection
  • Asset management
    • Console
    • Metadata
    • Version history
    • Packages and dependencies
  • DATA SERVICE
    • Overview
    • Create & edit Data Service
    • Data preview & download
    • Data sharing API
    • Access control
  • AI-powered
    • Rein AI Copilot
  • Settings
    • Organization settings
    • Project settings
    • Profile settings
    • Roles and permissions
  • Platform Specific
    • Doris/SelectDB
Powered by GitBook
On this page
  • Overview
  • Concept of Relationship
  • Why Setup a Relationship?
  • Define Relationships
  1. Semantic modeling
  2. Cube

Relationship

Overview

A Relationship in ReOrc defines how different Cubes are connected, enabling seamless data integration and enhancing analytical capabilities. Establishing relationships between Cubes ensures consistency, improves query performance, and facilitates the creation of meaningful Views.

Concept of Relationship

A Relationship represents the logical connection between two or more Cubes based on common keys. These relationships allow data from multiple Cubes to be combined, enabling cross-referencing and enriched analysis.

Types of Relationships:

  • One-to-One (1-1): Each record in one Cube corresponds to exactly one record in another Cube.

  • One-to-Many (1-n) or Many to One(n-1): A single record in one Cube is associated with multiple records in another Cube.

Why Setup a Relationship?

For View Creation

  • Relationships allow Views to aggregate and display data from multiple Cubes seamlessly.

  • Enables pre-joined datasets that improve performance in BI tools.

For Data Consistency and Integrity

  • Ensures correct data linkage across different datasets.

  • Reduces redundancy and improves maintainability.

For Enhanced Query Performance

  • Predefined relationships optimize query execution by reducing the need for complex joins at runtime.

  • Improves efficiency by leveraging indexed relationships for faster data retrieval.

Define Relationships

To define the relationship between cube, follow these steps:

  1. Click on the Edit Relationship button, the relationship modal will be shown

  1. Click on Add Relationship to start add a new row of the relationship between cube.

  2. Select the Relationship Type, From and To fields in the list and click on Add button.

  1. Once the relationships have been defined, click on the Save button to save all the relationships created.

PreviousCalculating Period-over-Period ChangesNextView

Last updated 15 days ago

Ensure the cube's primary key has been set before proceed to create the custom dimension. Refer

Create Cube