Closed
Bug 768531
Opened 13 years ago
Closed 12 years ago
[research] look at using django-haystack rather than elasticutils
Categories
(Participation Infrastructure :: Phonebook, defect)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: willkg, Unassigned)
References
Details
I don't know what the requirements for search are for mozillians, but I skimmed the code and don't see anything that suggests mozillians need elasticutils. Seems like mozillians would do fine with django-haystack.
Why switch? django-haystack is a more established library with lots of users and tests and all that and it's not in flux quite as much as elasticutils is at present.
Anyhow, this bug is for researching that and deciding whether to stick with elasticutils or switch to django-haystack.
Comment 1•13 years ago
|
||
The only question I really have is: Does Haystack support Elastic's Geo-type searches?
Reporter | ||
Comment 2•13 years ago
|
||
An exciting question!
1. Haystack does support geo searching.
I haven't used it, so I don't know if it supports everything you're looking for.
http://django-haystack.readthedocs.org/en/latest/spatial.html
However, one of the exciting things they say in there is that it requires at least ElasticSearch 0.17.7. We're running some kind of 0.17 in production in the cluster SUMO uses, but I don't know if it's 0.17.7. I also don't know if that's true of the cluster that Mozillians uses.
2. elasticutils doesn't support any geo anything, yet. Someone asked about it a month ago, but Rob and I haven't had any impetus to implement that since SUMO and AMO don't use it. That's not to say we will never implement it, but it will need to be implemented before Mozillians (or anyone else) could use it (obviously).
Comment 3•12 years ago
|
||
Based on meeting between Giorgos and Will, we decided to stick with elastic utils.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 4•12 years ago
|
||
Bumping to verified wontfix per comment 3 - dependent bugs have also been resolved.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•