Switch to Solr or Elasticsearch for Production about coursereviews HOT 12 CLOSED

Yeah... we should do this so we actually have a search.

from coursereviews.

I'm all about elasticsearch right now so that'd be my pick

from coursereviews.

Cool. I like it too. Do you know if we'd have to pay for it on Heroku?

from coursereviews.

yeah probably

On Thursday, August 28, 2014, Dana Silver [email protected] wrote:

Cool. I like it too. Do you know if we'd have to pay for it on Heroku?

—
Reply to this email directly or view it on GitHub
#16 (comment)
.

Sent from the phone.

from coursereviews.

I used bonsai for a while, then switched to found.

from coursereviews.

What kind of search are we looking for?

from coursereviews.

Courses and professors. Just for the homepage or the catalog.

from coursereviews.

What's wrong with typeahead with links?

from coursereviews.

Nothing and it's usually enough, but if you hit enter without clicking one of the typeaheads, you get no results.

from coursereviews.

That said, we could just make nothing happen and have people rely on the typeahead and catalog.

from coursereviews.

Down the road we'll probably want course description searching so I don't see elasticsearch as a bad move.

The way I'd recommend us implementing this would be by using

• ElasticUtils - https://elasticutils.readthedocs.org/en/latest/django.html
• Found Elasticsearch - https://www.found.no/

The reason for this is the the ElasticUtils project is awesome and will save us a bunch of time, but it's a little behind on the Elasticsearch release cycle -- it's incompatible with the latest version. Found elasticsearch offers the choice to use older versions. Right now the latest version ElasticUtils is compatible with is 1.1.0.

from coursereviews.

Using the full text search features of PostgreSQL as of fab71e1 with https://github.com/coursereviews/djorm-ext-pgfulltext. Seems to be working fine without a full-fledged search engine.

from coursereviews.