Closed Bug 544381 Opened 16 years ago Closed 16 years ago

Need job that can import Socorro crash report .jsonz files into HBase

Categories

(Mozilla Metrics :: Hadoop/HBase Operations, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED
Unreviewed

People

(Reporter: dre, Assigned: tbuckner)

Details

(Whiteboard: Desired due date 2010-02-10)

Input should be a list of jsonz files to import Processing should unzip them and insert the data into a new or existing crash report record as part of an appropriate column family
The cooked json files outputted by the processor differ in both content and key names. I'm going to created a new column called processed_data:jsonz or something similar. A potential side effect could be that any new processing rules for the eventual background processor that we might want to apply to all existing reports won't affect processed records that came in via thrit. We could also attempt to recover the raw json metadata from the jsonz file, though I'm not sure that's entirely possible.
Checked-in in socorro trunk/tools/loadjsonz.py I'm having some path problems when I execute it as a script rather than importing it as a module. Any ideas ozten?
(In reply to comment #2) We are good here, right? Also mentioned in the meeting - much of the data from report/index is populated from the jsonz file. http://crash-stats.mozilla.com/report/index/ec144062-6d72-4adc-8582-b18022100210 (some data like extension urls, bugzilla ids, etc are not directly in the jsonz)
We are good. If we can get some files of the form uuid TAB jsonz_file_path we can start loading. Do you know what all we need besides the jsonz?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: 2010-08.1 → ---
You need to log in before you can comment on or make changes to this bug.