Version history
D.Hub records changes to collections and multiple asset types as versions. Entry points and preview and restoration support differ by asset, so review the table below before taking action.
When the version is created
- When a resource is created, its initial version is recorded.
- Changing an alias, tags, description, or asset configuration creates a new version.
- Previous versions are not deleted.
Version History Tab
Open Version History on an asset details or editor screen to see versions in chronological order.
Each version entry displays the following information:
| Item | Description |
|---|---|
| Version Label | v1, v2 … Serial number (full version number is displayed when you hover the mouse over it) |
| Latest | Badge whether it is the latest version |
| Modified time | Time when the version was created (relative time + total time) |
| Author | Who created that version (preview owner when hovering over avatar) |
On the left, version statistics are displayed, including the total number of versions and the last modification time.
Preview and restore by asset
| Asset | Entry point | Preview | Restore |
|---|---|---|---|
| Collection | Version History in Collection Overview | Collection metadata | Supported |
| Dataset | Version History in details | Data sample or separate metadata change history | Restore data versions and metadata separately |
| Code | Version History in details | Code content; metadata changes are shown separately | Supported; comparison and download are also available |
| Pipeline | Version History in details | Alias, type, description, tags, and step configuration | Supported |
| Knowledge | Version History in details | Knowledge configuration | Supported |
| Knowledge document | Document section on the Knowledge version screen | Individual document version | Use the document-specific actions shown on the screen |
| Dashboard | Dashboard Version History in collection details | Widget and setting difference summary and snapshot | Supported |
| Agent | Agent Version History in collection details | Model, tool, prompt, and other configuration | Supported |
| Tool and actor | Version History in each editor | Runtime configuration | Supported |
| Semantic table | Version History in the editor | Column, metric, and description statistics and snapshot | Supported |
| Connector | Version History in the editor | Connection configuration | Supported |
| Ontology entity and relationship | Version history in the Builder properties panel | Change timeline | Read-only |
Select Preview on a version to inspect its configuration. For an asset that displays Restore, Restore version, or Restore metadata, continue through the confirmation dialog to save the selected state as the current version.
Dataset Data versions and Metadata changes are different histories. Restoring metadata reverts only alias, description, tags, options, and schema; it does not change table data. Collections and code also distinguish metadata changes from asset-content versions.
Restore overwrites the current state with the selected version. Before restoring a tool or actor, review referencing agents and redeploy any running agents after saving. After restoring a dashboard, pipeline, connector, or another asset, verify consumer screens and execution results.
Compare and download code versions
The Version History tab in code resources provides additional functionality.
- Version comparison: Select one version to compare it with the immediately preceding version. The oldest version has no predecessor, so only its selected content appears. Switch between Side-by-side / Unified, and review added and removed line counts.
- Download: Download the code file of the selected version as
.pyor.sql.
Line comparison in Side-by-side or Unified view and file download are available only for code. Use configuration preview and restoration on each screen for other assets.
References for each resource
- Dataset: Review data snapshots and metadata changes under Datasets.
- Code: Review content comparison, download, and separate metadata history under Code.
- Pipeline: Preview step configuration, then review runtime settings under Pipelines in a collection.
- Agents, tools, and actors: After restoring, review redeployment requirements under Apply changes by redeploying.
- Semantic tables: Review connection, column, and metric configuration under Semantic tables.
- Ontology: The timeline in Ontology Builder is read-only and does not use the general restoration procedure.
Next steps
- Dataset — Schema and data management of dataset
- Code — Code artifact management
- Pipelines (Collection) — Check pipeline status
- Pipeline Execution — Batch execution and monitoring