The default bug view has changed. See this FAQ.

rename blob schema # to something less confusing

ASSIGNED
Unassigned

Status

Release Engineering
Balrog: Backend
P3
normal
ASSIGNED
5 years ago
3 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [balrog])

(Reporter)

Description

5 years ago
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?
(Reporter)

Updated

4 years ago
Whiteboard: [balrog
(Reporter)

Updated

4 years ago
Whiteboard: [balrog → [balrog]
(Reporter)

Comment 1

4 years ago
Not going to be worked on soon.
Assignee: bhearsum → nobody
Priority: -- → P3
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 2

4 years ago
mass component change
Component: General Automation → Balrog: Backend
(Reporter)

Comment 3

3 years ago
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.
You need to log in before you can comment on or make changes to this bug.