-
Notifications
You must be signed in to change notification settings - Fork 50
feat: migrate google-cloud-datastore/java into java-datastore #427
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
------------------ - GQL support. - Metadata query support. - Command line tool improvements. - Microsoft Windows support (`gcd.cmd`). - Testing mode. - More intuitive `update_indexes` command (renamed to `updateindexes`). - New `create` command and simplified `start` command. - Improved integration with existing App Engine applications. - Ruby samples. - Java helper for query splitting.
------------------ - API changes: - `BlindWrite` method merged into `Commit`. - Added `list_value` to `Value` and changed `value` to a non-repeated field in `Property`. - In JSON API, string constants are now uppercase and underscore-separated instead of camel-cased (e.g. `LESS_THAN_OR_EQUAL` instead of `lessThanOrEqual`). - GQL changes: - New synthetic literals: `BLOB`, `BLOBKEY`, `DATETIME`, `KEY`. - Support for `IS NULL`. - Fixed partition ID handling for binding arguments. - Documentation changes: - All documentation has been updated to the v1beta2 API. - Getting started guide for Node.js now uses v0.4.5 of google-api-nodejs-client. - Fixed partition ID handling for query requests that include an explicit partition ID. - Fixed scopes in discovery document. - googleapis/google-cloud-datastore#9 - Fixed an issue where command line tool didn't work for some locales. - googleapis/google-cloud-datastore#12
java: add http initializer proto: better comments
In the class comment, the example code was invoking the wrong methods: datastore.stopDatastore() is named datastore.stop() datastore.clearDatastore() is named datastore.clear()
Change-Id: I045ae46d2ac2c4a8685ed8538137a8dbdf94028d
… now that the feature has been released. Bump proto library version to 1.5. Bump proto client version to 1.5. Bump google-http-client version to 1.23. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=171906809
This will allow connection reuse on errors where there was an actual response but the HTTP response code was not 200. This applies to cases where ESF returned an error or forwarded one from the backend (e.g. validation errors, contention, etc.). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=179095258
Note: this uses an AtomicReference to avoid synchronized static methods (and the class-level lock they entail). ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=180584318
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
Warning: This pull request is touching the following templated files:
|
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
4 similar comments
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly. In order to pass this check, please resolve this problem and then comment ℹ️ Googlers: Go here for more info. |
|
@BenWhitehead I didn't include the parent pom in https://github.com/googleapis/google-cloud-datastore/tree/master/java and instead switched the parent to this repo's pom. Let me know if you have any concerns. |
| <artifactId>datastore-v1-proto-client</artifactId> | ||
| <version>1.6.3</version> | ||
| <version>1.6.4-SNAPSHOT</version><!-- {x-version-update:datastore-v1-proto-client:current} --> | ||
| <exclusions> |
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.
You may be able to remove this exclusion now that the protos are from this build instead of from maven central.
|
LGTM, changing parent poms should be fine. Most of the dependencies for the datastore-v1 client were bom managed anyway at this point. One small comment where the pom may be able to be cleaned up, but not a blocker. |
chingor13
left a comment
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.
Ensure to regular merge or rebase merge if you want to keep individual commit histories.
source: https://github.com/googleapis/google-cloud-datastore/tree/master/java/datastore