Resource: Featurestore
Vertex AI feature Store provides a centralized repository for organizing, storing, and serving ML features. The Featurestore is a top-level container for your features and their values.
JSON representation |
---|
{ "name": string, "createTime": string, "updateTime": string, "etag": string, "labels": { string: string, ... }, "onlineServingConfig": { object ( |
Fields | |
---|---|
name |
Output only. name of the Featurestore. Format: |
createTime |
Output only. timestamp when this Featurestore was created. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
updateTime |
Output only. timestamp when this Featurestore was last updated. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
etag |
Optional. Used to perform consistent read-modify-write updates. If not set, a blind "overwrite" update happens. |
labels |
Optional. The labels with user-defined metadata to organize your Featurestore. label keys and values can be no longer than 64 characters (Unicode codepoints), can only contain lowercase letters, numeric characters, underscores and dashes. International characters are allowed. See https://goo.gl/xmQnxf for more information on and examples of labels. No more than 64 user labels can be associated with one Featurestore(System labels are excluded)." System reserved label keys are prefixed with "aiplatform.googleapis.com/" and are immutable. |
onlineServingConfig |
Optional. Config for online storage resources. The field should not co-exist with the field of |
state |
Output only. state of the featurestore. |
onlineStorageTtlDays |
Optional. TTL in days for feature values that will be stored in online serving storage. The feature Store online storage periodically removes obsolete feature values older than |
encryptionSpec |
Optional. Customer-managed encryption key spec for data storage. If set, both of the online and offline data storage will be secured by this key. |
OnlineServingConfig
OnlineServingConfig specifies the details for provisioning online serving resources.
JSON representation |
---|
{
"fixedNodeCount": integer,
"scaling": {
object ( |
Fields | |
---|---|
fixedNodeCount |
The number of nodes for the online store. The number of nodes doesn't scale automatically, but you can manually update the number of nodes. If set to 0, the featurestore will not have an online store and cannot be used for online serving. |
scaling |
Online serving scaling configuration. Only one of |
Scaling
Online serving scaling configuration. If minNodeCount and maxNodeCount are set to the same value, the cluster will be configured with the fixed number of node (no auto-scaling).
JSON representation |
---|
{ "minNodeCount": integer, "maxNodeCount": integer, "cpuUtilizationTarget": integer } |
Fields | |
---|---|
minNodeCount |
Required. The minimum number of nodes to scale down to. Must be greater than or equal to 1. |
maxNodeCount |
The maximum number of nodes to scale up to. Must be greater than minNodeCount, and less than or equal to 10 times of 'minNodeCount'. |
cpuUtilizationTarget |
Optional. The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80. When a cluster's CPU utilization exceeds the target that you have set, Bigtable immediately adds nodes to the cluster. When CPU utilization is substantially lower than the target, Bigtable removes nodes. If not set or set to 0, default to 50. |
State
Possible states a featurestore can have.
Enums | |
---|---|
STATE_UNSPECIFIED |
Default value. This value is unused. |
STABLE |
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 |
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, onlineServingConfig.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 fixedNodeCount 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 fixedNodeCount . The featurestore is still usable in this state. |
Methods |
|
---|---|
|
Batch reads Feature values from a Featurestore. |
|
Creates a new Featurestore in a given project and location. |
|
Deletes a single Featurestore. |
|
Gets details of a single Featurestore. |
|
Gets the access control policy for a resource. |
|
Lists Featurestores in a given project and location. |
|
Updates the parameters of a single Featurestore. |
|
Searches Features matching a query in a given project. |
|
Sets the access control policy on the specified resource. |
|
Returns permissions that a caller has on the specified resource. |