Class State (1.50.0)

Version 1.50.0

• 1.52.0 (latest)
• 1.51.0
• 1.50.0
• 1.49.0
• 1.48.0
• 1.47.0
• 1.46.0
• 1.45.0
• 1.44.0
• 1.43.0
• 1.39.0
• 1.38.1
• 1.37.0
• 1.36.4
• 1.35.0
• 1.34.0
• 1.33.1
• 1.32.0
• 1.31.1
• 1.30.1
• 1.29.0
• 1.28.1
• 1.27.1
• 1.26.1
• 1.25.0
• 1.24.1
• 1.23.0
• 1.22.1
• 1.21.0
• 1.20.0
• 1.19.1
• 1.18.3
• 1.17.1
• 1.16.1
• 1.15.1
• 1.14.0
• 1.13.1
• 1.12.1
• 1.11.0
• 1.10.0
• 1.9.0
• 1.8.1
• 1.7.1
• 1.6.2
• 1.5.0
• 1.4.3
• 1.3.0
• 1.2.0
• 1.1.1
• 1.0.1
• 0.9.0
• 0.8.0
• 0.7.1
• 0.6.0
• 0.5.1
• 0.4.0
• 0.3.1

State(value)

Possible states a featurestore can have.

Enum values:

STATE_UNSPECIFIED (0):
    Default value. This value is unused.
STABLE (1):
    State when the featurestore configuration is
    not being updated and the fields reflect the
    current configuration of the featurestore. The
    featurestore is usable in this state.
UPDATING (2):
    The state of the featurestore configuration when it is being
    updated. During an update, the fields reflect either the
    original configuration or the updated configuration of the
    featurestore. For example,
    `online_serving_config.fixed_node_count` can take minutes
    to update. While the update is in progress, the featurestore
    is in the UPDATING state, and the value of
    `fixed_node_count` can be the original value or the
    updated value, depending on the progress of the operation.
    Until the update completes, the actual number of nodes can
    still be the original value of `fixed_node_count`. The
    featurestore is still usable in this state.

Methods

State

State(value)

Possible states a featurestore can have.

Enum values:

STATE_UNSPECIFIED (0):
    Default value. This value is unused.
STABLE (1):
    State when the featurestore configuration is
    not being updated and the fields reflect the
    current configuration of the featurestore. The
    featurestore is usable in this state.
UPDATING (2):
    The state of the featurestore configuration when it is being
    updated. During an update, the fields reflect either the
    original configuration or the updated configuration of the
    featurestore. For example,
    `online_serving_config.fixed_node_count` can take minutes
    to update. While the update is in progress, the featurestore
    is in the UPDATING state, and the value of
    `fixed_node_count` can be the original value or the
    updated value, depending on the progress of the operation.
    Until the update completes, the actual number of nodes can
    still be the original value of `fixed_node_count`. The
    featurestore is still usable in this state.