-
Notifications
You must be signed in to change notification settings - Fork 44
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
feat: support readTime in Datastore query splitter. #763
feat: support readTime in Datastore query splitter. #763
Conversation
datastore-v1-proto-client/src/main/java/com/google/datastore/v1/client/QuerySplitterImpl.java
Show resolved
Hide resolved
...-proto-client/src/main/java/com/google/datastore/v1/client/testing/MockDatastoreFactory.java
Outdated
Show resolved
Hide resolved
...-proto-client/src/main/java/com/google/datastore/v1/client/testing/MockDatastoreFactory.java
Outdated
Show resolved
Hide resolved
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.
also, we can fix clirr by adding the method to a clirr-ignored-differences.xml
like /~https://github.com/googleapis/java-datastore/blob/main/google-cloud-datastore/clirr-ignored-differences.xml (since we added a default method, this is okay)
Done |
🤖 I have created a release *beep* *boop* --- ## [2.9.0](v2.8.0...v2.9.0) (2022-06-22) ### Features * support readTime in Datastore query splitter. ([#763](#763)) ([61758e0](61758e0)) ### Documentation * **sample:** clean up README for native image sample ([#771](#771)) ([7358aa3](7358aa3)) ### Dependencies * update dependency org.graalvm.buildtools:junit-platform-native to v0.9.12 ([#773](#773)) ([cab7e54](cab7e54)) * update dependency org.graalvm.buildtools:native-maven-plugin to v0.9.12 ([#774](#774)) ([496c1bc](496c1bc)) --- This PR was generated with [Release Please](/~https://github.com/googleapis/release-please). See [documentation](/~https://github.com/googleapis/release-please#release-please).
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> ☕️
If you write sample code, please follow the samples format.