From ab80b429c5d7e2933f53d8cff444230e428c5196 Mon Sep 17 00:00:00 2001 From: Abhin Chhabra Date: Wed, 5 Oct 2022 09:48:27 -0400 Subject: [PATCH] Minor fix to Bigtable documentation. Feedback from Danny mentioned that Bigtable should be able to store multiple versions of the same key and fetch the latest at read time. This makes sense and means that concurrent writes should work just fine. Signed-off-by: Abhin Chhabra --- docs/reference/online-stores/bigtable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/online-stores/bigtable.md b/docs/reference/online-stores/bigtable.md index d03426e102..0d6e7cfb13 100644 --- a/docs/reference/online-stores/bigtable.md +++ b/docs/reference/online-stores/bigtable.md @@ -46,7 +46,7 @@ Below is a matrix indicating which functionality is supported by the Bigtable on | readable by Java | no | | readable by Go | no | | support for entityless feature views | yes | -| support for concurrent writing to the same key | no | +| support for concurrent writing to the same key | yes | | support for ttl (time to live) at retrieval | no | | support for deleting expired data | no | | collocated by feature view | yes |