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

Add feature to support auto-migration for both ArangoDB and ElasticSearch #11

Open
sigma1326 opened this issue Sep 8, 2022 · 0 comments
Assignees
Labels
ArangoDB Related to ArangoDB bug Something isn't working ElasticSearch Related to ElasticSearch enhancement New feature or request

Comments

@sigma1326
Copy link
Member

The current database schema does not support auto-migration. When the codebase gets larger, it will be much harder to update both databases according to the new changes. It is better to have a mechanism to automatically detect changes in the schema and add necessary updates if possible. Only changes that cannot be solved using the auto-migration tool should be shown to the user. Moreover, this mechanism should check whether the new schema can be updated without any error.

@sigma1326 sigma1326 added bug Something isn't working enhancement New feature or request labels Sep 8, 2022
@sigma1326 sigma1326 self-assigned this Sep 16, 2022
@sigma1326 sigma1326 added ArangoDB Related to ArangoDB ElasticSearch Related to ElasticSearch labels Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ArangoDB Related to ArangoDB bug Something isn't working ElasticSearch Related to ElasticSearch enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant