Research: Implementing Elastic Search

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: openjck, Unassigned)

Tracking

Details

(Whiteboard: p=2 c=Site_search)

(Reporter)

Description

6 years ago
This is a subtask of bug 823723.

We mentioned reaching out to the SUMO and AMO teams for perspective on implementing elastic search before moving forward with using it to replace in-site search. After we have a few specific questions to ask, I will bring them into the discussion here so that we can capture the discussion.
(Reporter)

Updated

6 years ago
Summary: Research: How do SUMO and AMO → Research: Implementing Elastic Search
(Reporter)

Comment 1

6 years ago
Hey everyone. We are starting work on using Elastic Search on the MDN. I was wondering if you (or some members of your team) could answer a few questions our developers have about getting started. If possible, we would like to have this discussion here so that we can have a convenient record of it.

As a starter, we were wondering if you could share any insight on where we should start the code for indexing documents.
(In reply to John Karahalis [:openjck] from comment #1)
> Hey everyone. We are starting work on using Elastic Search on the MDN. I was
> wondering if you (or some members of your team) could answer a few questions
> our developers have about getting started. If possible, we would like to
> have this discussion here so that we can have a convenient record of it.
> 
> As a starter, we were wondering if you could share any insight on where we
> should start the code for indexing documents.

Assuming you're using ElasticUtils, there's the documentation: http://elasticutils.readthedocs.org/en/latest/

We've got several sites using ElasticUtils:

* Fjord: https://github.com/mozilla/fjord/tree/master/fjord/search
* Kitsune: https://github.com/mozilla/kitsune/blob/master/apps/search/es_utils.py
* Mozillians: https://github.com/mozilla/mozillians/blob/master/apps/users/models.py

Of the three of those, I think Fjord is "best-of-breed" at the moment. We're going to update Kitsune soon to catch up with ElasticUtils master tip and ditch a ton of code in the process.

Also, we talked about ElasticSearch and the options in bug #793010.

If you're going the django-haystack route, I use it in richard, but my code kind of sucks.
(Reporter)

Comment 3

6 years ago
Somehow forgot that we talked a bit about this in bug 793010. Thanks for jogging my memory.

Anyway, thanks for the detailed information. I will let the team decide if they have any last questions to ask before we get started on implementation.
(Reporter)

Comment 4

6 years ago
Looks like we have enough to get started. Will let you know if we have any more questions.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.