Closed Bug 1330120 Opened 9 years ago Closed 6 years ago

Fix case for 'payload' path in get_pings_properties in moztelemetry

Categories

(Data Platform and Tools :: General, defect, P2)

Product:
Data Platform and Tools
Component:
General
Type:
defect
Points:
1

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bugzilla, Unassigned)

References

Details

Currently, if you run: `get_pings_properties(pings, ['payload'])` You'll get: `IndexError: list index out of range` on this line: https://github.com/mozilla/python_moztelemetry/blob/0290df8b4904681da1a7dc49a01d27028e8346b5/moztelemetry/spark.py#L345 This is because a path that starts with 'payload' is shifted up one depth, so a path that's just 'payload' ends up with an empty array as its path: https://github.com/mozilla/python_moztelemetry/blob/0290df8b4904681da1a7dc49a01d27028e8346b5/moztelemetry/spark.py#L339 Likely, you'd never want to retrieve *just* 'payload' from the main ping, but this might make sense to do on one of the auxiliary pings (such as testpilot, which was what I was doing when I ran into this issue.)
Points: --- → 1
Priority: -- → P2
Component: Metrics: Pipeline → Telemetry APIs for Analysis
Product: Cloud Services → Data Platform and Tools

RIP moztelemetry

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