Skip to content

Custom Versioning of Datasets #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Custom Versioning of Datasets #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/schema-history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,12 @@ version. Some fields were even modified and had a type change at the latest vers
* [getSchemaBlame](../graphql/queries.md#getSchemaBlame)
* [getSchemaVersionList](../graphql/queries.md#getSchemaVersionList)

## Dataset Versioning

- **Automatic Versioning**: DataHub automatically manages the versioning of datasets. Each time a dataset's metadata or schema is updated, DataHub increments the version internally to track changes over time.
- **Manual Versioning**: Users cannot manually set or alter the version of a dataset within DataHub's internal versioning system.
- **Custom Version Tracking**: Users can track custom versions or external versioning schemes using custom metadata fields or tags. For example, you can annotate datasets with custom version information by adding a metadata field like `customVersion` and setting it to your desired version string.

## FAQ and Troubleshooting

**What updates are planned for the Schema History feature?**
Expand Down