Class State (2.38.0)

2.38.0 (latest) 2.35.0 2.34.0 2.33.0 2.32.0 2.31.0 2.30.0 2.29.1 2.28.0 2.27.3 2.26.1 2.25.2 2.23.1 2.22.0 2.21.5 2.20.3 2.19.8 2.18.4 2.17.1 2.16.1 2.15.2 2.14.1 2.13.12 2.12.1 2.11.1 2.10.0 2.9.0 2.8.0 2.7.1 2.6.1 2.5.0 2.4.2 2.3.0 2.2.0 2.1.0 2.0.0 1.7.2 1.6.1 1.5.0 1.4.3 1.3.1 1.2.0 1.1.0 1.0.2 0.45.0 0.44.0 0.43.0

State(value)

Possible states for a Bigtable subscription. Note: more states could be added in the future. Please code accordingly.

    - The Pub/Sub service agent has not been granted the
      `appropriate Bigtable IAM permission
      bigtable.tables.mutateRows <{$universe.dns_names.final_documentation_domain}/bigtable/docs/access-control#permissions>`__
    - The bigtable.googleapis.com API is not enabled for the
      project
      (`instructions <{$universe.dns_names.final_documentation_domain}/service-usage/docs/enable-disable>`__)
SCHEMA_MISMATCH (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.
IN_TRANSIT_LOCATION_RESTRICTION (6):
    Cannot write to the destination because enforce_in_transit
    is set to true and the destination locations are not in the
    allowed regions.
VERTEX_AI_LOCATION_RESTRICTION (7):
    Cannot write to Bigtable because the table is not in the
    same location as where Vertex AI models used in
    `message_transform`\ s are deployed.

Enums
Name	Description
STATE_UNSPECIFIED	Default value. This value is unused.
ACTIVE	The subscription can actively send messages to Bigtable.
NOT_FOUND	Cannot write to Bigtable because the instance, table, or app profile does not exist.
APP_PROFILE_MISCONFIGURED	Cannot write to Bigtable because the app profile is not configured for single-cluster routing.
PERMISSION_DENIED	Cannot write to Bigtable because of permission denied errors. This can happen if: