Job to populate only the important columns for making addon recommendation into hbase instance that TAAR will use. Should be modelled after this job: https://github.com/mozilla/telemetry-batch-view/blob/647abfb7f014995267360a50f8bacee788737b2f/src/main/scala/com/mozilla/telemetry/views/HBaseMainSummaryView.scala documentation here: https://docs.google.com/document/d/1c6S786IA88Ga0NOlZiEEQj071AOTwyVZUeZYyihZNw0/edit
depends on 1380713
Component: General → General
Product: Cloud Services → Data Platform and Tools
Other than the features outlined in bug 1380713, we also need to add the addonDetails column described here . @aswan, as of now, the |addonDetails| field in telemetry seems to report information about installed legacy and disabled addons. Are you aware of any plan to not send this information in Firefox 57? Will we still have data about installed legacy addons when 57 goes live? If you're not the right person to answer this, could you point me to who could?  - http://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/data/main-ping.html#addondetails  - https://dxr.mozilla.org/mozilla-central/search?q=setTelemetryDetails&case=true
In 57, legacy addons will remain installed but disabled. Among other things, this means that the author of a legacy extension can create a WebExtension version and provide it as an update, and the browser will install it just like any other extension update. I don't know of any plans to change anything that would affect the information that is available to telemetry about disabled addons.
Assignee: nobody → alessio.placitelli
Priority: -- → P1
The PRs were reviewed and merged and they are pushing data to the HBase instance.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → FIXED
Moved to new component, per bug 1425844.
Component: General → Add-on Recommender
You need to log in before you can comment on or make changes to this bug.