Closed Bug 791336 Opened 12 years ago Closed 5 years ago

rename blob schema # to something less confusing

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P5)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

References

Details

(Whiteboard: [lang=python][ready])

Catlee was telling me today that folks weren't quite sure what the 'schema_version' of the blob was for. What it is is a way to tell the difference between newer and older versions of the JSON blob that we store in the database. For example, if we rip out 'fakePartials' from the JSON at some point we'll want to increment the schema version so that things that parse it can expect not to have it in the newer version. Maybe blobVersion is a better name?
Whiteboard: [balrog
Whiteboard: [balrog → [balrog]
Not going to be worked on soon.
Assignee: bhearsum → nobody
Priority: -- → P3
Product: mozilla.org → Release Engineering
mass component change
Component: General Automation → Balrog: Backend
We might want to do this as part of bug 1021021, where we're adding a completely different schema (ie, doesn't precede or follow any of the current ones). We should probably use something that suggests there's not a linear line of blob types.
Mentor: bhearsum
Priority: P3 → P5
Whiteboard: [balrog] → [lang=python][ready]
Mentor: bhearsum
No assignee, updating the status.
Status: ASSIGNED → NEW
No assignee, updating the status.
No assignee, updating the status.
No assignee, updating the status.

Probably never going to do this.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.