We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For migration to Clearmash we will need to modify all backend calls to use the new Elasticsearch instead of Mongo
It would help to have a list of features in the backend, prioritized by how often they are used / how important they are.
Focus should be on removing mongo (which is also handled in another issue), and also a lot of the migration code.
The text was updated successfully, but these errors were encountered:
Here is what we have so far. Please pardon the mess, t'is a work in progress. https://docs.google.com/document/d/1JAn4qcTIAvmws4Qod0Zn5TFDeA-6YLQk05pWTUZiaAo/edit?usp=sharing
Sorry, something went wrong.
No branches or pull requests
For migration to Clearmash we will need to modify all backend calls to use the new Elasticsearch instead of Mongo
It would help to have a list of features in the backend, prioritized by how often they are used / how important they are.
Focus should be on removing mongo (which is also handled in another issue), and also a lot of the migration code.
The text was updated successfully, but these errors were encountered: