Cloud PubSub V1 Client - Class State (2.19.0)

Reference documentation and code samples for the Cloud PubSub V1 Client class State.

Possible states for a Bigtable subscription.

Note: more states could be added in the future. Please code accordingly.

Protobuf type google.pubsub.v1.BigtableConfig.State

Namespace

Google \ Cloud \ PubSub \ V1 \ BigtableConfig

Methods

static::name

Parameter
Name Description
value mixed

static::value

Parameter
Name Description
name mixed

Constants

STATE_UNSPECIFIED

Value: 0

Default value. This value is unused.

Generated from protobuf enum STATE_UNSPECIFIED = 0;

ACTIVE

Value: 1

The subscription can actively send messages to Bigtable.

Generated from protobuf enum ACTIVE = 1;

NOT_FOUND

Value: 2

Cannot write to Bigtable because the instance, table, or app profile does not exist.

Generated from protobuf enum NOT_FOUND = 2;

APP_PROFILE_MISCONFIGURED

Value: 3

Cannot write to Bigtable because the app profile is not configured for single-cluster routing.

Generated from protobuf enum APP_PROFILE_MISCONFIGURED = 3;

PERMISSION_DENIED

Value: 4

Cannot write to Bigtable because of permission denied errors.

This can happen if:

Generated from protobuf enum PERMISSION_DENIED = 4;

SCHEMA_MISMATCH

Value: 5

Cannot write to Bigtable because of a missing column family ("data") or if there is no structured row key for the subscription name + message ID.

Generated from protobuf enum SCHEMA_MISMATCH = 5;

IN_TRANSIT_LOCATION_RESTRICTION

Value: 6

Cannot write to the destination because enforce_in_transit is set to true and the destination locations are not in the allowed regions.

Generated from protobuf enum IN_TRANSIT_LOCATION_RESTRICTION = 6;

VERTEX_AI_LOCATION_RESTRICTION

Value: 7

Cannot write to Bigtable because the table is not in the same location as where Vertex AI models used in message_transforms are deployed.

Generated from protobuf enum VERTEX_AI_LOCATION_RESTRICTION = 7;