-
Notifications
You must be signed in to change notification settings - Fork 192
Support configuring default DurabilityLevel, PersistTo, ReplicateTo values #1063
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
Comments
Building on this, there is also no current way to specify the durability for a To reinforce the configurability requirement above, when testing locally developers typically have a single node cluster, but when deploying in production you want to ensure that data hits more than a single node. This may preclude using an annotation on the Repository level. Unless it reads configuration via a SpEL expression. |
Starting in spring-data-couchbase-4.3.0-M2 repository.withOptions(Upsert/ReplaceOptions).save(...) will be supported. Should be here by the end of the week: |
Annotations could be added in the future (similar to ScanConsistency) - on methods, repository and entity. |
Durability annotation to be added in the same places as ScanConsistency. |
In our organization it's rare that we require specific durability per document, typically it's the same across all our documents and even projects.
It would be nice if we could drive this by a configuration property in
application.properties
, though I expect Spring Boot to actually contain that logic viaCouchbaseDataProperties
, but it would be nice if Spring Data Couchbase exposed a way to supply these values.The text was updated successfully, but these errors were encountered: