| Index: common/gcloud/pubsub/topic.go
|
| diff --git a/common/gcloud/pubsub/topic.go b/common/gcloud/pubsub/topic.go
|
| index 262e6d6ad9e6b4169d9b02b50ac45c7e9351adfa..e10e95ce9c8a7a195585500ff522fb83913933e8 100644
|
| --- a/common/gcloud/pubsub/topic.go
|
| +++ b/common/gcloud/pubsub/topic.go
|
| @@ -16,8 +16,6 @@ package pubsub
|
|
|
| import (
|
| "flag"
|
| -
|
| - "cloud.google.com/go/pubsub"
|
| )
|
|
|
| // Topic is a fully-qualified Pub/Sub project/topic name.
|
| @@ -61,17 +59,3 @@ func (t Topic) SplitErr() (p, n string, err error) {
|
| p, n, err = resourceProjectName(string(t))
|
| return
|
| }
|
| -
|
| -// DisableTopicBundling configures a new pubsub.Topic to not bundle its data.
|
| -//
|
| -// t must NOT have had any Publish calls made yet, else these settings will not
|
| -// have any effect.
|
| -//
|
| -// By default, a Pub/Sub Topic bundles data, delaying its actual dispatch in
|
| -// favor of batching calls. Sometimes this is not desired. This function
|
| -// configures an existing Topic not to bundle.
|
| -func DisableTopicBundling(t *pubsub.Topic) {
|
| - t.PublishSettings.DelayThreshold = 0
|
| - t.PublishSettings.NumGoroutines = 1
|
| - t.PublishSettings.CountThreshold = 1
|
| -}
|
|
|