commit | 09ba3f8614bab8557260ba47b7bd3a7ec711991a | [log] [tgz] |
---|---|---|
author | Jean de Klerk <deklerk@google.com> | Fri Jun 07 17:02:15 2019 -0600 |
committer | Alex Hong <hongalex@google.com> | Tue Mar 17 21:30:10 2020 +0000 |
tree | b31b268ddc488278885029886d36d1454b9615d5 | |
parent | 2b70e299e1adf430d29a20a555c3f1eda0f2f2cb [diff] |
pubsub: add ordered keys Note: this is available as a beta. Users can access it with `go get cloud.google.com/go/pubsub@v1.1.0-beta.ordered.keys`. Note: design doc is available at go/pubsub-ordered-keys-go. For users, this change involves: - PublishSettings.NumGoroutines and ReceiveSettings.NumGoroutines should both result in about double the number of goroutines, since an additional data structure (publish/receive scheduler) uses that value. Documentation has been adjusted accordingly to describe it more as a scaling factor than an exact number. - Default ReceiveSettings.NumGoroutines is increased from 1 to 10. It's generally a better experience to have multiple workers than one. And, some tests - like TestStreamingPullFlowControl - implicitly require it. - Since ordered keys require only a single outstanding RPC at once, it is possible to send ordered key messages to Topic.Publish (and subsequently to PublishScheduler.Add) faster than the bundler can publish them to the Pub/Sub service, resulting in a backed up queue of Pub/Sub bundles. Each item in the bundler queue is a goroutine, which means users may see thousands of goroutines in debugging they might do. - There may be slightly slower processing speeds due to additional data structures. A future CL will include a Resume method. Change-Id: Ib710944d557970290cf12321d1fdbd9b1699231d Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/41770 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Jean de Klerk <deklerk@google.com> Reviewed-by: Jonathan Amsterdam <jba@google.com>
Go packages for Google Cloud Platform services.
import "cloud.google.com/go"
To install the packages on your system, do not clone the repo. Instead:
Change to your project directory:
cd /my/cloud/project
Get the package you want to use. Some products have their own module, so it's best to go get
the package(s) you want to use:
$ go get cloud.google.com/go/firestore # Replace with the package you want to use.
NOTE: Some of these packages are under development, and may occasionally make backwards-incompatible changes.
NOTE: Github repo is a mirror of https://code.googlesource.com/gocloud.
Alpha status: the API is still being actively developed. As a result, it might change in backward-incompatible ways and is not recommended for production use.
Beta status: the API is largely complete, but still has outstanding features and bugs to be addressed. There may be minor backwards-incompatible changes where necessary.
Stable status: the API is mature and ready for production use. We will continue addressing bugs and feature requests.
Documentation and examples are available at pkg.go.dev/cloud.google.com/go
We support the two most recent major versions of Go. If Google App Engine uses an older version, we support that as well.
By default, each API will use Google Application Default Credentials for authorization credentials used in calling the API endpoints. This will allow your application to run in many environments without requiring explicit configuration.
client, err := storage.NewClient(ctx)
To authorize using a JSON key file, pass option.WithCredentialsFile
to the NewClient
function of the desired package. For example:
client, err := storage.NewClient(ctx, option.WithCredentialsFile("path/to/keyfile.json"))
You can exert more control over authorization by using the golang.org/x/oauth2
package to create an oauth2.TokenSource
. Then pass option.WithTokenSource
to the NewClient
function: snip:# (auth-ts)
tokenSource := ...
client, err := storage.NewClient(ctx, option.WithTokenSource(tokenSource))
Contributions are welcome. Please, see the CONTRIBUTING document for details. We‘re using Gerrit for our code reviews. Please don’t open pull requests against this repo, new pull requests will be automatically closed.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.