Use pyelasticsearch instead of pyes

RESOLVED FIXED in 2013-05-16

Status

Marketplace
Search
P1
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: robhudson, Assigned: robhudson)

Tracking

2013-05-16
Points:
---
Dependency tree / graph

Details

(Whiteboard: p=2)

(Assignee)

Description

4 years ago
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)

Updated

4 years ago
Blocks: 851588
(Assignee)

Comment 1

4 years ago
First step... isolate AMO code that depends on elasticutils using pyes:
https://github.com/mozilla/zamboni/commit/5b9c9ec
(Assignee)

Updated

4 years ago
Depends on: 861420
(Assignee)

Comment 2

4 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

4 years ago
Priority: -- → P1
(Assignee)

Comment 3

4 years ago
This went out as part of bug 867288.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-05-16
You need to log in before you can comment on or make changes to this bug.