Closed
Bug 1401969
Opened 8 years ago
Closed 8 years ago
Add normalized_os_version to validated pings
Categories
(Data Platform and Tools :: General, enhancement, P3)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Assigned: ashort)
References
Details
This can just match the regex in [0].
[0] https://github.com/mozilla/telemetry-streaming/commit/eb6f5278bc3686bc705dbd4938312ecc953ee917
Comment 1•8 years ago
|
||
This should be straightforward, since it's a direct function of the field value.
Setting priority to P3 for now since the quarter's just about out.
Points: --- → 2
Priority: -- → P3
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → ashort
Assignee | ||
Comment 2•8 years ago
|
||
Please review: https://github.com/mozilla-services/lua_sandbox_extensions/pull/177
Will this require adding fields to schemas in mozilla-pipeline-schemas?
Comment 3•8 years ago
|
||
Frank, if we add a new field to the "metadata" section in the direct-to-parquet outputs, that will break schema evolution in (some? all?) data sources, right?
Specifically, if we added this normalizedOSVersion field to somewhere like [1].
[1] https://github.com/mozilla-services/mozilla-pipeline-schemas/blob/9da6df743c4d02ffcf4d69cd56988ebb8f0942e0/schemas/telemetry/new-profile/new-profile.4.parquetmr.txt#L7
Flags: needinfo?(fbertsch)
Reporter | ||
Comment 4•8 years ago
|
||
Yes, it will break schema evolution. I would prefer we follow the approach suggested in bug 1403608.
Flags: needinfo?(fbertsch)
Comment 5•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Pipeline Ingestion → General
You need to log in
before you can comment on or make changes to this bug.
Description
•