-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
Feature: Enable schema management check via config for JaversMongoRepositories #1260
Comments
We also faced the same situation. Let's wait response) |
Hey @bartoszwalacik, |
thanks @egasimov , see my comment on the PR |
@bartoszwalacik Sure. I've made few changes, Could you please re-review it again ? Thank you for your time. |
Faced same issue, while integrating. Would appreciate having ability to control behavior via config file |
done, released in 6.10.0 |
Is your feature request related to a problem? Please describe.
When using Javers in projects backend by MongoDB, javers-mongo-repository module trying to create indexes on the collection. (via calling ensureSchema()). In our projects, the app-user usually do not have such permissions(create index) on database.
These internal used collections and indexes are considered to be created by Ops team.
Describe the solution you'd like
I would like to javers-mongo-repository module having option to configure schema management like javers-sql-repository module did
Describe alternatives you've considered
An alternative to create CustomMongoSchemaManager that extends MongoSchemaManager inject it into where used in library via reflection. But it is no so good option to consider.
Additional context
There is option to configure "enable schema management" in Javers SQL Repository module (see SqlRepositoryConfiguration.java).
The text was updated successfully, but these errors were encountered: