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 database import service/task #83

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

Elasticsearch database import service/task #83

brennanholtzclaw opened this issue Jun 8, 2016 · 1 comment

Comments

@brennanholtzclaw
Copy link
Contributor

brennanholtzclaw commented Jun 8, 2016

A service or task (or possibly after_save action) needs to be written for jobs to put them into the Elasticsearch Database.

  • The service should take in all new jobs as the existing rake task saves them into the Postgres DB.
  • The service/task should not duplicate entries and should only pull entries from the last 60 days.
  • The service/background worker should also clear out old jobs on the daily/weekly
@brennanholtzclaw brennanholtzclaw self-assigned this Jun 8, 2016
@brennanholtzclaw
Copy link
Contributor Author

Once this can be tested in production, it's basically good to go. I think a chron job of some kind still needs to be written to clear out the jobs older than 60 days, but that shouldn't be too bad.

I tried to deploy my own heroku app and setting up the Bonsai add-on. This is where things went poorly. Most of my time and problem solving went to figuring out what I was missing to set the application up correctly, and seed a production database.

Beyond that I started running into problems getting information to cURL into the Elasticsearch DB on Bonsai. At the time of writing, I'm really not sure if this was due to bad requests, or because the PostgreSQL database was never set up correctly, meaning the after_save action wouldn't work right.
I'm linking some good Bonsai resources here for future research and development.

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

No branches or pull requests

2 participants