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
  • Publish a version
  • View version history
  1. Asset management

Version history

PreviousMetadataNextPackages and dependencies

Last updated 15 days ago

Version history provides a systematic approach to keeping track of changes made to an asset in ReOrc. You can create and publish an asset under a specific version, allowing your team to review the progression of changes and roll back to previous versions if necessary.

Publish a version

By default, when you first create an asset, such as a model or a pipeline, that asset is in the draft state. After you've made some changes to the asset, you can publish it to indicate that the asset is ready for use in your data workflow. This means creating a version of the asset and recording it in version history.

To publish an asset, follow these steps:

  1. In the editor, click on the Publish button.

    This opens the asset publishing modal.

  2. In Version Information, provide the version number and the update message to describe the changes you made.

  3. If you're making changes to an already published asset, you can switch to the Compare changes tab to see the diff view.

    Diff view compares the current modifications to the latest version of the asset.

  4. Click Publish.

View version history

You can view all the versions of an asset in version history.

Follow these steps:

  1. Open the asset in the editor.

  2. Click on the Version history button.

  3. In the opened Version history panel, you can see the list of versions of the asset.

  4. Select a version to view the detailed changes.