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)
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)
| Assignee | ||
Comment 1•11 years ago
|
||
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).
Comment 2•11 years ago
|
||
(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.
| Reporter | ||
Comment 3•11 years ago
|
||
Bug triage comments: Looks like Pipeline team can't do this in Q1.
| Assignee | ||
Comment 4•11 years ago
|
||
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.
Updated•11 years ago
|
Priority: -- → P3
Comment 5•11 years ago
|
||
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.
Comment 6•11 years ago
|
||
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rvitillo
| Assignee | ||
Updated•11 years ago
|
No longer blocks: 1152539
Summary: Integrate Spark data flow → Add support for the new v4 ping data format in Spark
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Comment 8•11 years ago
|
||
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 → ---
Comment 9•11 years ago
|
||
Ah, sorry. I thought both were about reading Heka data in Spark.
| Assignee | ||
Comment 10•11 years ago
|
||
The Spark API supports now v4 submissions, see http://nbviewer.ipython.org/github/vitillo/emr-bootstrap-spark/blob/master/Telemetry%20Hello%20World%20%28v4%29.ipynb
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•