-
Notifications
You must be signed in to change notification settings - Fork 192
DATACOUCH-605 - Support ScanConsistency in n1ql queries #267
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
Conversation
mikereiche
commented
Oct 2, 2020
- You have read the Spring Data contribution guidelines.
- There is a ticket in the bug tracker for the project in our JIRA.
- You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
- You submit test cases (unit or integration tests) that back your changes.
- You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks good, just a couple minor notes
src/main/java/org/springframework/data/couchbase/core/ReactiveInsertByIdOperationSupport.java
Show resolved
Hide resolved
src/main/java/org/springframework/data/couchbase/core/ReactiveUpsertByIdOperationSupport.java
Show resolved
Hide resolved
* | ||
* @return queryScanConsistency | ||
*/ | ||
public QueryScanConsistency getConsistency() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need a public getter on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's used by ExecutableFindByQuerySupport.matching(Query) - if Query has scanConsistency set, it is taken from there instead of requiring a separate call to ExecutableFindByQuerySupport.consistentWith( scanConsistency ).
* @param queryScanConsistency | ||
* @return this | ||
*/ | ||
public Query with(final QueryScanConsistency queryScanConsistency) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be more like scanConsistency(..) ? we also name limit etc. explicitly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok - I changed it to scanConsistency(). But I was looking at with(Pageable) and with(Sort).
But that pattern breaks down for things like skip and limit which are just int.
b32746c
to
f246c3b
Compare
f246c3b
to
4862dcc
Compare