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
  • Run assets in console
  • Inspect task details
  1. Asset management

Console

PreviousData protectionNextMetadata

Last updated 15 days ago

The ReOrc Console offers a convenient way to run and verify your assets in the development environment. Instead of navigating between modules, you can access the console from the bottom toolbar to execute models and pipelines directly, viewing results instantly.

Similar to pipeline execution, a console run performs these actions:

  • Allow you to select multiple assets.

  • Execute each asset as a task in the order determined by dependency, and along with associated data tests (for models).

  • Provide task details view for troubleshooting, including the compiled query and run logs.

But unlike pipeline executions, console runs are instant and focused on verification. This makes it easy to iterate on your assets and ensure they work correctly before shipping changes to production.

The console currently supports two asset types: models and pipelines.

Run assets in console

To run assets in the console, follow these steps:

  1. Open your project and go to Design.

  2. At the bottom of the screen, click on Console.

    This opens the console panel.

  3. Click on the Choose assets or pipeline prompt input.

  4. In the opened pop-up, select the asset type and the target assets.

  5. In Variable settings, you can view the list of variables associated with the models.

    On each variable, you can decide to lock the current value; this applies to dynamic variables, such as current datetime. You can also provide a custom value.

  6. Click Save.

  7. To run the assets, click Run.

Each asset is then executed as a task and displayed in the task list.

Inspect task details

To view the details of a task, click on the task from the list. This opens the task details view where you can inspect the compiled query, the logs of materialization process, and the test results.