Update Service updates to new vector from inserted vector in the vald-agent
components.
service Update {
rpc Update(payload.v1.Update.Request) returns (payload.v1.Object.Location) {}
rpc StreamUpdate(payload.v1.Update.Request) returns (payload.v1.Object.StreamLocation) {}
rpc MultiUpdate(payload.v1.Update.MultiRequest) returns (payload.v1.Object.Locations) {}
rpc UpdateTimestamp(payload.v1.Update.TimestampRequest) returns (payload.v1.Object.Location) {}
}
Update RPC is the method to update a single vector.
-
the scheme of
payload.v1.Update.Request
message Update.Request { Object.Vector vector = 1; Update.Config config = 2; } message Object.Vector { string id = 1; repeated float vector = 2; int64 timestamp = 3; } message Update.Config { bool skip_strict_exist_check = 1; Filter.Config filters = 2; int64 timestamp = 3; bool disable_balanced_update = 4; } message Filter.Config { repeated Filter.Target targets = 1; } message Filter.Target { string host = 1; uint32 port = 2; }
-
Update.Request
field type label description vector Object.Vector The vector to be updated. config Update.Config The configuration of the update request. -
Object.Vector
field type label description id string The vector ID. vector float repeated The vector. timestamp int64 timestamp represents when this vector inserted. -
Update.Config
| field | type | label | description | | :---: | :--- | :---- | :---------- | | skip_strict_exist_check | bool | | A flag to skip exist check during update operation. | | filters | Filter.Config | | Filter configuration. | | timestamp | int64 | | Update timestamp. | | disable_balanced_update | bool | | A flag to disable balanced update (split remove -> insert operation)
during update operation. |
-
Filter.Config
field type label description targets Filter.Target repeated Represent the filter target configuration. -
Filter.Target
field type label description host string The target hostname. port uint32 The target port.
-
-
the scheme of
payload.v1.Object.Location
message Object.Location { string name = 1; string uuid = 2; repeated string ips = 3; }
-
Object.Location
field type label description name string The name of the location. uuid string The UUID of the vector. ips string repeated The IP list.
-
code | description |
---|---|
0 | OK |
1 | CANCELLED |
3 | INVALID_ARGUMENT |
4 | DEADLINE_EXCEEDED |
5 | NOT_FOUND |
6 | ALREADY_EXISTS |
10 | ABORTED |
13 | INTERNAL |
Please refer to Response Status Code for more details.
The request process may not be completed when the response code is NOT 0 (OK)
.
Here are some common reasons and how to resolve each error.
name | common reason | how to resolve |
---|---|---|
CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | Check the code, especially around timeout and connection management, and fix if needed. |
INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | Check Agent config, request payload, and fix request payload or Agent config. |
DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | Check the gRPC timeout setting on both the client and server sides and fix it if needed. |
NOT_FOUND | Requested ID is NOT inserted. | Send a request with an ID that is already inserted. |
ALREADY_EXISTS | Request pair of ID and vector is already inserted. | Change request ID. |
INTERNAL | Target Vald cluster or network route has some critical error. | Check target Vald cluster first and check network route including ingress as second. |
StreamUpdate RPC is the method to update multiple vectors using the bidirectional streaming RPC.
Using the bidirectional streaming RPC, the update request can be communicated in any order between client and server.
Each Update request and response are independent.
It's the recommended method to update the large amount of vectors.
-
the scheme of
payload.v1.Update.Request
message Update.Request { Object.Vector vector = 1; Update.Config config = 2; } message Object.Vector { string id = 1; repeated float vector = 2; int64 timestamp = 3; } message Update.Config { bool skip_strict_exist_check = 1; Filter.Config filters = 2; int64 timestamp = 3; bool disable_balanced_update = 4; } message Filter.Config { repeated Filter.Target targets = 1; } message Filter.Target { string host = 1; uint32 port = 2; }
-
Update.Request
field type label description vector Object.Vector The vector to be updated. config Update.Config The configuration of the update request. -
Object.Vector
field type label description id string The vector ID. vector float repeated The vector. timestamp int64 timestamp represents when this vector inserted. -
Update.Config
| field | type | label | description | | :---: | :--- | :---- | :---------- | | skip_strict_exist_check | bool | | A flag to skip exist check during update operation. | | filters | Filter.Config | | Filter configuration. | | timestamp | int64 | | Update timestamp. | | disable_balanced_update | bool | | A flag to disable balanced update (split remove -> insert operation)
during update operation. |
-
Filter.Config
field type label description targets Filter.Target repeated Represent the filter target configuration. -
Filter.Target
field type label description host string The target hostname. port uint32 The target port.
-
-
the scheme of
payload.v1.Object.StreamLocation
message Object.StreamLocation { Object.Location location = 1; google.rpc.Status status = 2; } message Object.Location { string name = 1; string uuid = 2; repeated string ips = 3; }
-
Object.StreamLocation
field type label description location Object.Location The vector location. status google.rpc.Status The RPC error status. -
Object.Location
field type label description name string The name of the location. uuid string The UUID of the vector. ips string repeated The IP list.
-
code | description |
---|---|
0 | OK |
1 | CANCELLED |
3 | INVALID_ARGUMENT |
4 | DEADLINE_EXCEEDED |
5 | NOT_FOUND |
6 | ALREADY_EXISTS |
10 | ABORTED |
13 | INTERNAL |
Please refer to Response Status Code for more details.
The request process may not be completed when the response code is NOT 0 (OK)
.
Here are some common reasons and how to resolve each error.
name | common reason | how to resolve |
---|---|---|
CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | Check the code, especially around timeout and connection management, and fix if needed. |
INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | Check Agent config, request payload, and fix request payload or Agent config. |
DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | Check the gRPC timeout setting on both the client and server sides and fix it if needed. |
NOT_FOUND | Requested ID is NOT inserted. | Send a request with an ID that is already inserted. |
ALREADY_EXISTS | Request pair of ID and vector is already inserted. | Change request ID. |
INTERNAL | Target Vald cluster or network route has some critical error. | Check target Vald cluster first and check network route including ingress as second. |
MultiUpdate is the method to update multiple vectors in 1 request.
Please be careful that the size of the request exceeds the limit.
-
the scheme of
payload.v1.Update.MultiRequest
message Update.MultiRequest { repeated Update.Request requests = 1; } message Update.Request { Object.Vector vector = 1; Update.Config config = 2; } message Object.Vector { string id = 1; repeated float vector = 2; int64 timestamp = 3; } message Update.Config { bool skip_strict_exist_check = 1; Filter.Config filters = 2; int64 timestamp = 3; bool disable_balanced_update = 4; } message Filter.Config { repeated Filter.Target targets = 1; } message Filter.Target { string host = 1; uint32 port = 2; }
-
Update.MultiRequest
field type label description requests Update.Request repeated Represent the multiple update request content. -
Update.Request
field type label description vector Object.Vector The vector to be updated. config Update.Config The configuration of the update request. -
Object.Vector
field type label description id string The vector ID. vector float repeated The vector. timestamp int64 timestamp represents when this vector inserted. -
Update.Config
| field | type | label | description | | :---: | :--- | :---- | :---------- | | skip_strict_exist_check | bool | | A flag to skip exist check during update operation. | | filters | Filter.Config | | Filter configuration. | | timestamp | int64 | | Update timestamp. | | disable_balanced_update | bool | | A flag to disable balanced update (split remove -> insert operation)
during update operation. |
-
Filter.Config
field type label description targets Filter.Target repeated Represent the filter target configuration. -
Filter.Target
field type label description host string The target hostname. port uint32 The target port.
-
-
the scheme of
payload.v1.Object.Locations
message Object.Locations { repeated Object.Location locations = 1; } message Object.Location { string name = 1; string uuid = 2; repeated string ips = 3; }
-
Object.Locations
field type label description locations Object.Location repeated -
Object.Location
field type label description name string The name of the location. uuid string The UUID of the vector. ips string repeated The IP list.
-
code | description |
---|---|
0 | OK |
1 | CANCELLED |
3 | INVALID_ARGUMENT |
4 | DEADLINE_EXCEEDED |
5 | NOT_FOUND |
6 | ALREADY_EXISTS |
10 | ABORTED |
13 | INTERNAL |
Please refer to Response Status Code for more details.
The request process may not be completed when the response code is NOT 0 (OK)
.
Here are some common reasons and how to resolve each error.
name | common reason | how to resolve |
---|---|---|
CANCELLED | Executed cancel() of rpc from client/server-side or network problems between client and server. | Check the code, especially around timeout and connection management, and fix if needed. |
INVALID_ARGUMENT | The Dimension of the request vector is NOT the same as Vald Agent's config, the requested vector's ID is empty, or some request payload is invalid. | Check Agent config, request payload, and fix request payload or Agent config. |
DEADLINE_EXCEEDED | The RPC timeout setting is too short on the client/server side. | Check the gRPC timeout setting on both the client and server sides and fix it if needed. |
NOT_FOUND | Requested ID is NOT inserted. | Send a request with an ID that is already inserted. |
ALREADY_EXISTS | Request pair of ID and vector is already inserted. | Change request ID. |
INTERNAL | Target Vald cluster or network route has some critical error. | Check target Vald cluster first and check network route including ingress as second. |
A method to update timestamp an indexed vector.
-
the scheme of
payload.v1.Update.TimestampRequest
message Update.TimestampRequest { string id = 1; int64 timestamp = 2; bool force = 3; }
-
Update.TimestampRequest
field type label description id string The vector ID. timestamp int64 timestamp represents when this vector inserted. force bool force represents forcefully update the timestamp.
-
-
the scheme of
payload.v1.Object.Location
message Object.Location { string name = 1; string uuid = 2; repeated string ips = 3; }
-
Object.Location
field type label description name string The name of the location. uuid string The UUID of the vector. ips string repeated The IP list.
-
code | description |
---|
TODO
Please refer to Response Status Code for more details.
TODO