-
Notifications
You must be signed in to change notification settings - Fork 88
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
spike: persistence/indexing into elasticsearch (and maybe sqlite) #4
Comments
One other reason for this is to have the minimum steps needed for local dev. Having anyone be able to For local dev it'd be nice to just |
Changed the title. Let's store the OFAC records in elasticsearch (ES) to get something going. If we need to store the watches let's use sqlite - I'm not thinking of ES as durable storage right now. |
I can take on deploying ES if no one else wants to, but I'd like to get people familiar with Kubernetes. |
We won't need ES storage for this, so that simplifies the app. |
A standalone instance of this app needs to download the OFAC files on its own and should refresh that copy after N hours. (N is configurable and likely defaults to 24h) This allows someone to start our app without the need for external dependencies and keeps the information up to date.
We can keep the files in temp storage close to the app. When the app restarts it can check the modification time of the files and if the files are too old download them again. This would help to prevent repeated downloads if the app is in a crash loop.
After reading the flat files we might want to persist the structured data in a database to allow for better queries, full text, etc. I think a SQL solution would be the best and we can start with sqlite since our other apps use that.
The spec for CSV files isn't too bad and can probably be directly mapped to a few tables.
ent_num
is used to join the tables together.The text was updated successfully, but these errors were encountered: