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
Copy file name to clipboardExpand all lines: docs/getting-started/faq.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,10 @@ No, there are [feature views without entities](concepts/data-model-and-concepts/
22
22
23
23
Feast currently does not support any access control other than the access control required for the Provider's environment \(for example, GCP and AWS permissions\).
24
24
25
+
### Does Feast support streaming sources?
26
+
27
+
Feast is actively working on this right now. Please reach out to the Feast team if you're interested in giving feedback!
28
+
25
29
### Does Feast support composite keys?
26
30
27
31
A feature view can be defined with multiple entities. Since each entity has a unique join\_key, using multiple entities will achieve the effect of a composite key.
@@ -30,6 +34,21 @@ A feature view can be defined with multiple entities. Since each entity has a un
30
34
31
35
Please see a detailed comparison of Feast vs. Tecton [here](https://www.tecton.ai/feast/). For another comparison, please see [here](https://mlops.community/learn/feature-store/).
32
36
37
+
### What are the performance/latency characteristics of Feast?
38
+
39
+
Feast is designed to work at scale and support low latency online serving. Benchmarks to be released soon, and active work is underway to support very latency sensitive use cases.
40
+
41
+
### Does Feast support embeddings and list features?
42
+
43
+
Yes. Specifically:
44
+
45
+
* Simple lists / dense embeddings:
46
+
* BigQuery supports list types natively
47
+
* Redshift does not support list types, so you'll need to serialize these features into strings \(e.g. json or protocol buffers\)
48
+
* Feast's implementation of online stores serializes features into Feast protocol buffers and supports list types \(see [reference](https://github.com/feast-dev/feast/blob/master/docs/specs/online_store_format.md#appendix-a-value-proto-format)\)
49
+
* Sparse embeddings \(e.g. one hot encodings\)
50
+
* One way to do this efficiently is to have a protobuf or string representation of [https://www.tensorflow.org/guide/sparse\_tensor](https://www.tensorflow.org/guide/sparse_tensor)
51
+
33
52
### Does Feast support X storage engine?
34
53
35
54
The list of supported offline and online stores can be found [here](../reference/offline-stores/) and [here](../reference/online-stores/), respectively. The [roadmap](../roadmap.md) indicates the stores for which we are planning to add support. Finally, our Provider abstraction is built to be extensible, so you can plug in your own implementations of offline and online stores. Please see more details about custom providers [here](../how-to-guides/creating-a-custom-provider.md).
0 commit comments