Skip to content
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

Jump to bottom

⚡️ Spike: investigate DataHub's versioning logic #2962

Closed
murdo-moj opened this issue Jan 16, 2024 · 3 comments
Closed

⚡️ Spike: investigate DataHub's versioning logic #2962

murdo-moj opened this issue Jan 16, 2024 · 3 comments
Assignees
@murdo-moj
Labels
spike investigation, discovery into a thing stale

Comments

@murdo-moj
Copy link
Contributor

murdo-moj commented Jan 16, 2024 •
edited by tom-webber
Loading

User Story

As a data consumer
I want to understand how data products get versioned
So that I can use the correct version of data

Value / Purpose

We need a writeup of the logic behind the versioning which datahub has, to compare with the current approach https://dsdmoj.atlassian.net/wiki/spaces/DataPlatform/pages/4479156541/Data+product+Schema+Versioning

DataHub docs links
https://datahubproject.io/docs/dev-guides/timeline/

https://datahubproject.io/docs/schema-history/

Proposal

No response

Definition of Done

Example - [ ] Documentation has been written / updated
@murdo-moj murdo-moj added enhancement enhancing an existing feature data-platform-labs labels Jan 16, 2024
@murdo-moj murdo-moj changed the title [zap] <Investigate DataHub's versioning logic> [zap] Investigate DataHub's versioning logic Jan 16, 2024
@murdo-moj murdo-moj changed the title [zap] Investigate DataHub's versioning logic [spark] Investigate DataHub's versioning logic Jan 16, 2024
@murdo-moj murdo-moj changed the title [spark] Investigate DataHub's versioning logic ⚡️ Investigate DataHub's versioning logic Jan 16, 2024
@murdo-moj murdo-moj added the spike investigation, discovery into a thing label Jan 16, 2024
@seanprivett seanprivett changed the title ⚡️ Investigate DataHub's versioning logic ⚡️ Spike: investigate DataHub's versioning logic Jan 18, 2024
@MatMoore MatMoore assigned MatMoore and unassigned MatMoore Jan 19, 2024
@seanprivett seanprivett removed enhancement enhancing an existing feature data-platform-labs labels Jan 22, 2024
@murdo-moj murdo-moj self-assigned this Jan 23, 2024
@murdo-moj murdo-moj moved this from Todo to In Progress in Data Catalogue Jan 23, 2024
@murdo-moj
Copy link
Contributor Author

https://dsdmoj.atlassian.net/wiki/spaces/DataPlatform/pages/4666360065/DataHub+s+versioning

@murdo-moj murdo-moj moved this from In Progress to Review in Data Catalogue Jan 23, 2024
@YvanMOJdigital YvanMOJdigital moved this from Review to Done in Data Catalogue Jan 25, 2024
@jemnery jemnery mentioned this issue Jan 25, 2024
Closed
@github-actions github-actions bot mentioned this issue Feb 1, 2024
Closed
@github-actions GitHub Actions
Copy link
Contributor

This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open.

@github-actions github-actions bot added the stale label Mar 24, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Apr 1, 2024

This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@murdo-moj murdo-moj

Labels
spike investigation, discovery into a thing stale
Projects
Data Catalogue
Status: Done ✅
Milestone
No milestone
Development

No branches or pull requests
4 participants
@MatMoore @jacobwoffenden @seanprivett @murdo-moj