Closed Bug 1412796 Opened 8 years ago Closed 8 years ago

Make TAAR use local and other details coming from AMO

Categories

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

Product:
Data Platform and Tools
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Dexter, Assigned: vng)

References

Details

The AMO page URI contains some more data that we can scavenge [1] in case the user is not yet in our pipeline. We can, at the very least, use the locale to suggest relevant add-ons if the client id cannot be found in HBase. This bug is about changing taar and taar-api to support parsing this additional data and using it in the locale recommender if client data cannot be found in HBase. [1] - http://searchfox.org/mozilla-central/rev/1ebd2eff44617df3b82eea7d2f3ca1b60cc591a0/browser/app/profile/firefox.js#51
Blocks: 1286215
Priority: -- → P2
Assignee: nobody → vng
This was fixed by the following PRs: - https://github.com/mozilla/taar-api/pull/17 - https://github.com/mozilla/taar/pull/51 And it was deployed to our dev instance :)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Moved to new component, per bug 1425844.
Component: General → Add-on Recommender
Component: Add-on Recommender → General
You need to log in before you can comment on or make changes to this bug.