You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
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 .
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.
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.
The text was updated successfully, but these errors were encountered: