-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support disabling consistent read on per @Query #9
Comments
Live on 5.2.2-SNAPSHOT on ossrh
Default does whatever the mapper has configured and is the default. Other keys are self explanatory. Leaving issue open for comments / suggestions |
@dragneelfps you get a chance to look at it? |
@boostchicken do you have any plans on creating a PR for the parent repository of Ill look into the changes and report back as soon as possible. |
@boostchicken instead of having an enum, can't we have a |
The problem with this is you have to put it on every annotation. Annotations can't have null values, they just have a default. By putting it to an enum we can have it be a default value which means change nothing. If we were to have an Boolean it would require you to adjust every query annotation and break the API significantly. |
Valid point.
|
I think its a little more verbose and confusing, only one annotation argument should be required. Also, a lot of people may never want to default to true or false. The default setting makes a lot of sense in my book |
Released in 5.2.2 |
Expected Behavior
We should be able to disable consistent read behaviour on per query basis, instead of having to use a custom repository.
This feature is helpful for queries on GSI as they dont support consistent reads.
Actual Behavior
Either disable it for all using dynamodb mapper config or use custom repositories.
Specifications
The text was updated successfully, but these errors were encountered: