Closed Bug 1375017 Opened 8 years ago Closed 6 years ago

Use Long for UintScalar types to avoid overflow

Categories

(Data Platform and Tools :: General, enhancement, P3)

Product:
Data Platform and Tools
Component:
General
Platform:
x86
macOS
Type:
enhancement
Points:
3

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bugzilla, Unassigned)

References

Details

Scala doesn't support unsigned integers so we currently don't support half the potential values of UintScalars. We should switch the scala + parquet representations of UintScalars to Long to avoid this issue.
Assignee: nobody → spenrose
Assignee: spenrose → nobody
Setting priority to P3. If we encounter an overflow issue, let's bump it up in priority.
Points: --- → 3
Priority: -- → P3
We seem to be getting overflow in the main_summary_first_paint simple measurement, which was just implemented as a scalar. Both are recorded as uint32_t, and should be moved to long's to avoid overflow. https://sql.telemetry.mozilla.org/queries/22552/source
See Also: → 1081924
Depends on: 1397402

Everything is bigint in bigquery!

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Component: Datasets: Main Summary → General
You need to log in before you can comment on or make changes to this bug.