-
Notifications
You must be signed in to change notification settings - Fork 41
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
New architecture; stop using Elasticsearch #30
Labels
Milestone
Comments
This was referenced Mar 9, 2018
Closed
Need also to update |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is quite a drastic change from before, but I think it's the right thing to do to get things going.
Drop the use of Elasticsearch (currently used only to manage projects) and switch to a simpler architecture where projects are defined in a configuration file (
projects.cfg
).This also means that we can drop the project management CLI and REST operations. Projects can be read-only.
The index functionality can be later implemented better using gensim and/or fastText. These will become backends and there can eventually be several backends per project, as defined in another configuration file (
backends.cfg
).The text was updated successfully, but these errors were encountered: