You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
entries | objects | Map of serving key of feature view as key and value of serving key as value. Serving key are a set of the primary key of feature groups which are included in the feature view query. If feature groups are joint with prefix, the primary key needs to be attached with prefix.
47
51
passedFeatures | objects | Optional. Map of feature name as key and feature value as value. This overwrites feature values in the response.
48
52
metadataOptions | objects | Optional. Map of metadataoption as key and boolean as value. Default metadata option is false. Metadata is returned on request. Metadata options available: 1\. featureName 2\. featureType |
53
+
options | objects | Optional. Map of option as key and boolean as value. Default option is false. Options available: 1\. validatePassedFeatures 2\. includeDetailedStatus
49
54
50
55
### Response
51
56
@@ -75,7 +80,17 @@ metadataOptions | objects | Optional. Map of metadataoption as key and bo
75
80
"featureType": "string"
76
81
}
77
82
],
78
-
"status": "COMPLETE"
83
+
"status": "COMPLETE",
84
+
"detailedStatus": [
85
+
{
86
+
"featureGroupId": 1,
87
+
"httpStatus": 200,
88
+
},
89
+
{
90
+
"featureGroupId": 2,
91
+
"httpStatus": 200,
92
+
},
93
+
]
79
94
}
80
95
```
81
96
@@ -124,6 +139,66 @@ metadataOptions | objects | Optional. Map of metadataoption as key and bo
124
139
}
125
140
```
126
141
142
+
**Detailed Status**
143
+
144
+
If `includeDetailedStatus` option is set to true, detailed status is returned in the response. Detailed status is a list of feature group id and http status code, corresponding to each read operations perform internally by RonDB. Meaning is as follows:
145
+
146
+
-`featureGroupId`: Id of the feature group, used to identify which table the operation correspond from.
147
+
-`httpStatus`: Http status code of the operation.
148
+
* 200 means success
149
+
* 400 means bad request, likely pk name is wrong or pk is incomplete. In particular, if pk for this table/feature group is not provided in the request, this http status is returned.
150
+
* 404 means no row corresponding to PK
151
+
* 500 means internal error.
152
+
153
+
Both `404` and `400` set the status to `MISSING` in the response. Examples below corresponds respectively to missing row and bad request.
154
+
155
+
156
+
Missing Row: The pk name,value was correctly passed but the corresponding row was not found in the feature group.
157
+
```
158
+
{
159
+
"features": [
160
+
36,
161
+
"2022-01-24",
162
+
null,
163
+
null
164
+
],
165
+
"status": "MISSING",
166
+
"detailedStatus": [
167
+
{
168
+
"featureGroupId": 1,
169
+
"httpStatus": 200,
170
+
},
171
+
{
172
+
"featureGroupId": 2,
173
+
"httpStatus": 404,
174
+
},
175
+
]
176
+
}
177
+
```
178
+
179
+
Bad Request e.g pk name,value pair for FG2 not provided or the corresponding column names was incorrect.
180
+
```
181
+
{
182
+
"features": [
183
+
36,
184
+
"2022-01-24",
185
+
null,
186
+
null
187
+
],
188
+
"status": "MISSING",
189
+
"detailedStatus": [
190
+
{
191
+
"featureGroupId": 1,
192
+
"httpStatus": 200,
193
+
},
194
+
{
195
+
"featureGroupId": 2,
196
+
"httpStatus": 400,
197
+
},
198
+
]
199
+
}
200
+
```
201
+
127
202
## Batch feature vectors
128
203
129
204
### Request
@@ -159,6 +234,10 @@ metadataOptions | objects | Optional. Map of metadataoption as key and bo
entries | `array<objects>` | Each items is a map of serving key as key and value of serving key as value. Serving key of feature view.
174
253
passedFeatures | `array<objects>` | Optional. Each items is a map of feature name as key and feature value as value. This overwrites feature values in the response. If provided, its size and order has to be equal to the size of entries. Item can be null.
175
254
metadataOptions | objects | Optional. Map of metadataoption as key and boolean as value. Default metadata option is false. Metadata is returned on request. Metadata options available: 1\. featureName 2\. featureType
255
+
options | objects | Optional. Map of option as key and boolean as value. Default option is false. Options available: 1\. validatePassedFeatures 2\. includeDetailedStatus
176
256
177
257
### Response
178
258
179
259
```
180
260
{
261
+
{
181
262
"features": [
182
263
[
183
264
16,
@@ -193,9 +274,9 @@ metadataOptions | objects | Optional. Map of metadataoption as key a
193
274
],
194
275
[
195
276
71,
196
-
"2022-01-22",
197
-
"int3",
198
-
"str97"
277
+
null,
278
+
null,
279
+
null
199
280
],
200
281
[
201
282
48,
@@ -231,9 +312,31 @@ metadataOptions | objects | Optional. Map of metadataoption as key a
231
312
"status": [
232
313
"COMPLETE",
233
314
"COMPLETE",
234
-
"COMPLETE",
315
+
"MISSING",
235
316
"COMPLETE",
236
317
"COMPLETE"
318
+
],
319
+
"detailedStatus": [
320
+
[{
321
+
"featureGroupId": 1,
322
+
"httpStatus": 200,
323
+
}],
324
+
[{
325
+
"featureGroupId": 1,
326
+
"httpStatus": 200,
327
+
}],
328
+
[{
329
+
"featureGroupId": 1,
330
+
"httpStatus": 404,
331
+
}],
332
+
[{
333
+
"featureGroupId": 1,
334
+
"httpStatus": 200,
335
+
}],
336
+
[{
337
+
"featureGroupId": 1,
338
+
"httpStatus": 200,
339
+
}]
237
340
]
238
341
}
239
342
```
@@ -246,6 +349,7 @@ note: Order of the returned features are the same as the order of entries in the
0 commit comments