Bidirectional streaming RPC to directly write to feature values in a feature view. Requests may not have a one-to-one mapping to responses and responses may be returned out-of-order to reduce latency.
Endpoint
posthttps://{service-endpoint}/v1beta1/{featureView}:directWrite
Where {service-endpoint}
is one of the supported service endpoints.
Path parameters
featureView
string
FeatureView resource format projects/{project}/locations/{location}/featureOnlineStores/{featureOnlineStore}/featureViews/{featureView}
Request body
The request body contains data with the following structure:
Required. The data keys and associated feature values.
Response body
Response message for FeatureOnlineStoreService.FeatureViewDirectWrite
.
If successful, the response body contains data with the following structure:
Response status for the keys listed in FeatureViewDirectWriteResponse.write_responses
.
The error only applies to the listed data keys - the stream will remain open for further [FeatureOnlineStoreService.FeatureViewDirectWriteRequest][] requests.
Partial failures (e.g. if the first 10 keys of a request fail, but the rest succeed) from a single request may result in multiple responses - there will be one response for the successful request keys and one response for the failing request keys.
Details about write for each key. If status is not OK, WriteResponse.data_key
will have the key with error, but WriteResponse.online_store_write_time
will not be present.
JSON representation |
---|
{ "status": { object ( |
DataKeyAndFeatureValues
A data key and associated feature values to write to the feature view.
The data key.
List of features to write.
JSON representation |
---|
{ "dataKey": { object ( |
Feature
feature name & value pair.
name
string
feature short name.
data_oneof
Union type
data_oneof
can be only one of the following:feature value and timestamp.
JSON representation |
---|
{
"name": string,
// data_oneof
"valueAndTimestamp": {
object ( |
FeatureValueAndTimestamp
feature value and timestamp.
The feature value.
The feature timestamp to store with this value. If not set, then the feature Store server will generate a timestamp when it receives the write request.
Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: "2014-10-02T15:01:23Z"
, "2014-10-02T15:01:23.045123456Z"
or "2014-10-02T15:01:23+05:30"
.
JSON representation |
---|
{
"value": {
object ( |
WriteResponse
Details about the write for each key.
What key is this write response associated with.
When the feature values were written to the online store. If FeatureViewDirectWriteResponse.status
is not OK, this field is not populated.
Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: "2014-10-02T15:01:23Z"
, "2014-10-02T15:01:23.045123456Z"
or "2014-10-02T15:01:23+05:30"
.
JSON representation |
---|
{
"dataKey": {
object ( |