Closed
Bug 1437127
Opened 8 years ago
Closed 4 years ago
Create changeset for datasets
Categories
(Data Platform and Tools :: Documentation and Knowledge Repo (RTMO), enhancement, P4)
Data Platform and Tools
Documentation and Knowledge Repo (RTMO)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: frank, Unassigned)
Details
This should focus on breaking changes and version bumps. Eventually we can think about including non-breaking changes (e.g. "Column $NAME has been available since 2018-01-01").
The use case is, given an older query that you're looking to reproduce, it's broken. This should be the first line viewing for finding how that dataset changed.
Updated•8 years ago
|
Points: --- → 2
Priority: -- → P4
Comment 1•4 years ago
|
||
is this still an issue you see? and something you think we should prioriotize in next year?
if not - let's close it and refile if it comes higher in priroity.
Flags: needinfo?(fbertsch)
| Reporter | ||
Comment 2•4 years ago
|
||
I don't think this is necessary. There were more breaking changes in Parquet than there are in BQ.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(fbertsch)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•