Closed Bug 1125451 Opened 11 years ago Closed 11 years ago

Add support for the new v4 ping data format in Spark

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kparlante, Assigned: rvitillo)

References

Details

- rvitillo has been exploring spark (http://robertovitillo.com/tag/spark/); integrate this into the pipeline - Implies a similar db-backed table of datastore filenames for filtering (don’t want to list S3 every time - too slow)
Katie, I am not listing the filenames manually, I am using mreid's db-backed service (http://ec2-54-203-209-235.us-west-2.compute.amazonaws.com:8080/files).
(In reply to rvitillo@mozilla.com from comment #1) > Katie, I am not listing the filenames manually, I am using mreid's db-backed > service > (http://ec2-54-203-209-235.us-west-2.compute.amazonaws.com:8080/files). Right, this is a reminder that we should do the same for the new data on S3 too.
Bug triage comments: Looks like Pipeline team can't do this in Q1.
Mark, can you can provide me with a python module that given a file that uses the new data format returns a list of strings with the payloads? If so I should be able to integrate it easily with Spark.
Priority: -- → P3
Here is some code that reads the new data format - it returns the actual Heka message objects. The JSON data is in a field called "Payload", though some of the other message fields are likely to be of interest as well. There is probably no reason to include the "raw" or "header" pieces when integrating with Spark.
Assignee: nobody → rvitillo
Depends on: 1134217
Blocks: 1152539
No longer blocks: 1152539
Summary: Integrate Spark data flow → Add support for the new v4 ping data format in Spark
Depends on: 1154308
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
I don't see this as a duplicate: this bug is about adding support to read Heka objects in Spark while Bug 1152539 is about adding a client API to Spark.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Blocks: 1147395
Ah, sorry. I thought both were about reading Heka data in Spark.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.