Support multiple features per key in firestore format spec (#1374)

Signed-off-by: Oleg Avdeev <oleg.v.avdeev@gmail.com>
feast-dev · Mar 9, 2021 · 964f3a5 · 964f3a5
1 parent e313455
commit 964f3a5
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 1 deletion.
diff --git a/docs/specs/firebase_online_example.monopic b/docs/specs/firebase_online_example.monopic
diff --git a/docs/specs/firebase_online_example.png b/docs/specs/firebase_online_example.png
diff --git a/docs/specs/online_store_format.md b/docs/specs/online_store_format.md
@@ -68,7 +68,7 @@ We use the following structure to store feature data in the Firestore:
 * second level, in each project-collection, there is a Firebase document for each Feature Table
 * third level, in the document for the Feature Table, there is a subcollection called `values` that contain a document per feature row. That document contains the following fields:
   * `key` contains entity key as serialized `feast.types.EntityKey` proto
-  * `value` contains value as serialized `feast.types.Value` proto
+  * `values` contains feature name to value map, values serialized as `feast.types.Value` proto
   * `event_ts` contains event timestamp (in the native firestore timestamp format)
   * `created_ts` contains write timestamp (in the native firestore timestamp format)