Skip to content

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

Closed
wants to merge 1 commit into from

Conversation

mikereiche
Copy link
Collaborator

  • 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).

@mikereiche mikereiche requested a review from daschl October 2, 2020 04:36
Copy link
Contributor

@daschl daschl left a 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

*
* @return queryScanConsistency
*/
public QueryScanConsistency getConsistency() {
Copy link
Contributor

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?

Copy link
Collaborator Author

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) {
Copy link
Contributor

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.

Copy link
Collaborator Author

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.

@mikereiche mikereiche force-pushed the datacouch_605_scanconsistency_option branch from b32746c to f246c3b Compare October 2, 2020 23:17
@mikereiche mikereiche force-pushed the datacouch_605_scanconsistency_option branch from f246c3b to 4862dcc Compare October 3, 2020 00:14
@mikereiche mikereiche closed this Oct 5, 2020
@mikereiche mikereiche deleted the datacouch_605_scanconsistency_option branch October 16, 2020 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants