1 Star 0 Fork 0

Arohat / google-cloud-go

Name
Message
Commit message
Actions
spanner: Make a new release v1.1.0. Change-Id: I188a387f7830a1dc438f0b7074d625b360fcea43 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47770 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Shanika Kuruppu <skuruppu@google.com> Reviewed-by: Knut Olav Løite <koloite@gmail.com> Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-11-01 16:23
storage: release v1.2.1 Change-Id: Id8a23a640cfe147281d9316c5b48f97af6746a81 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47971 Reviewed-by: Jean de Klerk <deklerk@google.com> Reviewed-by: Frank Natividad <franknatividad@google.com> Reviewed-by: kokoro <noreply+kokoro@google.com>
2019-11-06 11:54
storage: release v1.2.0 Change-Id: I340008e9849c65dfcb00bcb58036a5877d825ff3 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47871 Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-11-05 15:02
bigtable: release bigtable/v1.1.0 This change will be tagged bigtable/v1.1.0 Change-Id: I60780bc8ceddd1e5301e8b479b5a5ee6a4c1422e Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47690 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-10-29 22:04
bigquery: release bigquery/v1.2.0 This change will be tagged bigquery/v1.2.0 Change-Id: Ifefdcdd75cb8220d3f45c4920937bc1918c509e6 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47514 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chris Broadfoot <cbro@google.com>
2019-10-28 20:05
storage: release new version Change-Id: I57f8b56a2fc9b4e201580f4e628cb7e31c171796 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47271 Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-10-22 17:32
storage: release v1.1.1 Change-Id: I3cac9469c29d1a18c2a13f02b8075d2bedabfa6e Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/46970 Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-10-15 09:33
all: release v0.47.0 Change-Id: I6214dee30fe470c923737a73bd7724032fc122fc Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/46830 Reviewed-by: Noah Dietz <ndietz@google.com>
2019-10-11 10:37
pubsub: add ordered keys Pub/Sub ordered keys requires: - Publish with a non-empty key gets added to a per-key queue, as implemented by Bundler.HandlerLimit=1. This setting causes the bundler to only have one outstanding bundle being handled at a time; further bundles form a queue. - Receive with a message that has a non-empty key gets added to a per-key queue, as implemented by a slice. When a worker operates on a key, it processes all items in the key's slice until the slice is empty, at which point it deletes the key to release the key's resources, and the worker returns to the worker pool. Functionally, for users, this should involve: - Slightly slower processing speeds due to additional data structures along the Publish and Receive paths. (we should do some performance testing to vet this out) - PublishSettings.NumGoroutines and ReceiveSettings.NumGoroutines should both result in 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. TODO: add Resume method. Change-Id: Ib710944d557970290cf12321d1fdbd9b1699231d
2019-06-07 17:02
pubsub: add ordered keys Pub/Sub ordered keys requires: - Publish with a non-empty key gets added to a per-key queue, as implemented by Bundler.HandlerLimit=1. This setting causes the bundler to only have one outstanding bundle being handled at a time; further bundles form a queue. - Receive with a message that has a non-empty key gets added to a per-key queue, as implemented by a slice. When a worker operates on a key, it processes all items in the key's slice until the slice is empty, at which point it deletes the key to release the key's resources, and the worker returns to the worker pool. Functionally, for users, this should involve: - Slightly slower processing speeds due to additional data structures along the Publish and Receive paths. (we should do some performance testing to vet this out) - PublishSettings.NumGoroutines and ReceiveSettings.NumGoroutines should both result in 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. TODO: add Resume method. Change-Id: Ib710944d557970290cf12321d1fdbd9b1699231d
2019-06-07 17:02
bigquery: release v1.1.0 This CL will be tagged bigquery/v1.1.0. Change-Id: Iea16adf679d069738690c952ea5092c8c986c3d9 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/46591 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Jean de Klerk <deklerk@google.com>
2019-10-08 21:20
docs: update RELEASING.md Also fix tidyall.sh to actually tidy all modules. Change-Id: Id4d9f6996aeeeb907e204ba95c64e856f2b9f485 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/46191 Reviewed-by: Noah Dietz <ndietz@google.com>
2019-10-01 14:45
storage: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create storage/CHANGES.md 2. Create storage/go_mod_tidy_hack.go 3. Run: cd storage go mod init cloud.google.com/go/storage go mod edit -require cloud.google.com/go@v0.46.3 go mod edit -replace cloud.google.com/go@v0.46.3=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.3 cd .. go mod tidy This CL will be tagged v0.46.3 and storage/v1.0.0. Change-Id: I05acd70e81f58e8c9aff5a5f9517b860856a5209 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/45491 Reviewed-by: Noah Dietz <ndietz@google.com>
2019-09-13 13:24
storage: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create storage/CHANGES.md 2. Create storage/go_mod_tidy_hack.go 3. Run: cd storage go mod init cloud.google.com/go/storage go mod edit -require cloud.google.com/go@v0.46.3 go mod edit -replace cloud.google.com/go@v0.46.3=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.3 cd .. go mod tidy This CL will be tagged v0.46.3 and storage/v1.0.0. Change-Id: I05acd70e81f58e8c9aff5a5f9517b860856a5209 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/45491 Reviewed-by: Noah Dietz <ndietz@google.com>
2019-09-13 13:24
spanner: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create spanner/CHANGES.md 2. Create spanner/go_mod_tidy_hack.go 3. Run: cd spanner go mod init cloud.google.com/go/spanner go mod edit -require cloud.google.com/go@v0.46.2 go mod edit -replace cloud.google.com/go@v0.46.2=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.2 cd .. go mod tidy This CL will be tagged v0.46.2 and spanner/v1.0.0. Change-Id: I5ad1a4694dfc866d31a23386101fac13d8c9bc56 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/45450 Reviewed-by: Chris Broadfoot <cbro@google.com> Reviewed-by: kokoro <noreply+kokoro@google.com>
2019-09-13 11:39
spanner: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create spanner/CHANGES.md 2. Create spanner/go_mod_tidy_hack.go 3. Run: cd spanner go mod init cloud.google.com/go/spanner go mod edit -require cloud.google.com/go@v0.46.2 go mod edit -replace cloud.google.com/go@v0.46.2=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.2 cd .. go mod tidy This CL will be tagged v0.46.2 and spanner/v1.0.0. Change-Id: I5ad1a4694dfc866d31a23386101fac13d8c9bc56 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/45450 Reviewed-by: Chris Broadfoot <cbro@google.com> Reviewed-by: kokoro <noreply+kokoro@google.com>
2019-09-13 11:39
firestore: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create firestore/CHANGES.md 2. Create firestore/go_mod_tidy_hack.go 3. Run: cd firestore go mod init cloud.google.com/go/firestore go mod edit -require cloud.google.com/go@v0.46.1 go mod edit -replace cloud.google.com/go@v0.46.1=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.1 cd .. go mod tidy This CL will be tagged v0.46.1 and firestore/v1.0.0. Change-Id: Id833e807fe78942b78dc30606e6500b4bf7cd169 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/44870 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Emmanuel Odeke <emm.odeke@gmail.com>
2019-09-04 15:05
firestore: carve out module Reasons for carve out: - It allows us to communicate client stability with semver, instead of all clients being contained in a mega v0.Y.Z module. - It allows us to separate the per-client dependencies. This CL was created by: 1. Create firestore/CHANGES.md 2. Create firestore/go_mod_tidy_hack.go 3. Run: cd firestore go mod init cloud.google.com/go/firestore go mod edit -require cloud.google.com/go@v0.46.1 go mod edit -replace cloud.google.com/go@v0.46.1=../ go mod tidy go mod edit -dropreplace cloud.google.com/go@v0.46.1 cd .. go mod tidy This CL will be tagged v0.46.1 and firestore/v1.0.0. Change-Id: Id833e807fe78942b78dc30606e6500b4bf7cd169 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/44870 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Emmanuel Odeke <emm.odeke@gmail.com>
2019-09-04 15:05
all: release v0.46.0 This will be tagged v0.46.0. Change-Id: I860145c716b96a52f3d210934ceb6d0daf1c1a21 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/45430 Reviewed-by: Tyler Bui-Palsulich <tbp@google.com>
2019-09-13 11:01
pubsub: fix package name in go_mod_tidy_hack.go This will be tagged pubsub/v1.0.1. Change-Id: Ifd6d6b2fd181872197265fa81b0b904e47edbc2e Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/44851 Reviewed-by: Alex Hong <hongalex@google.com>
2019-09-04 14:58
1
https://gitee.com/arohat/google-cloud-go.git
git@gitee.com:arohat/google-cloud-go.git
arohat
google-cloud-go
google-cloud-go

Search