Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elasticsearch front-facing search bar #84

Open
brennanholtzclaw opened this issue Jun 8, 2016 · 1 comment
Open

Elasticsearch front-facing search bar #84

brennanholtzclaw opened this issue Jun 8, 2016 · 1 comment
Labels

Comments

@brennanholtzclaw
Copy link
Contributor

A search bar on the main page of the app should take in user input and search all fields in the ES database for hits.
The Elasticsearch Database will respond with JSON objects of relevant results.

@brennanholtzclaw
Copy link
Contributor Author

I never made it to this step because of just hilarious problems with deploying Elasticseaarch to a Heroku add-on.

I'm going to throw out a couple assumptions I was working with. Take these for what you will:

  1. We'll have two databases
  • Basically the process on my branches assumes that current rake tasks will continue to run and load data into a Postgres DB for historical tracking. The Elasticsearch DB would then be populated by those tasks (inadvertently), as well, and used as the front-facing DB for user interaction. It would (ideally) only hold the last 60-ish days of jobs and provide Ngram matching for auto-complete and suggestions.
  1. ES doesn't need to worry about models
    • Because we're not using this as the sole DB, Elasticsearch doesn't need to worry about properly indexing attributes on models. That should all be taken care of in the service provided in Elasticsearch database import service/task #83 .
  2. Searching will need to be done across multiple fields
    • This is kind of a given, but the whole point to adding ES is for full-text search across all attributes on each job object. You could get fancy and add Multi-String searching, but you probably don't need it. However, the query snippet posted in that link is probably much smaller than what you'll need to write for the full-text search.

It seems daunting, but remember that ES basically is just an API and deals with everything like a JSON object.

Here are a few more solid resources to use in your deep-dive into Elasticsearch.

Enjoy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants