Closed
Bug 857156
Opened 12 years ago
Closed 11 years ago
Use pyelasticsearch instead of pyes
Categories
(Marketplace Graveyard :: Search, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-05-16
People
(Reporter: robhudson, Assigned: robhudson)
References
Details
(Whiteboard: p=2)
This is a step towards upgrading to elasticutils 0.7, which uses pyelasticsearch.
First we can drop in pyelasticsearch into the requirements and update AMO to use this to get an ES object rather than using pyes' `get_es`. AMO doesn't use elasticutils yet so it just needs an ES connection to be used in its own ES wrapper code. When AMO is all good, we can safely focus on MKT side.
Assignee | ||
Comment 1•11 years ago
|
||
First step... isolate AMO code that depends on elasticutils using pyes:
https://github.com/mozilla/zamboni/commit/5b9c9ec
Assignee | ||
Comment 2•11 years ago
|
||
I pushed this forward a bit this week:
https://github.com/robhudson/zamboni/compare/elasticutils-upgrade
Next steps are tests and to update mkt search code to use the new index and the elasticutils lib. There's also a bug in the reindexing code that triggers an elasticsearch timeout error.
Assignee | ||
Updated•11 years ago
|
Priority: -- → P1
Assignee | ||
Comment 3•11 years ago
|
||
This went out as part of bug 867288.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → 2013-05-16
You need to log in
before you can comment on or make changes to this bug.
Description
•