Elasticsearch
Description
The ElasticSearch online store provides support for materializing tabular feature values, as well as embedding feature vectors, into an ElasticSearch index for serving online features. The embedding feature vectors are stored as dense vectors, and can be used for similarity search. More information on dense vectors can be found here.
Getting started
In order to use this online store, you'll need to run pip install 'feast[elasticsearch]'. You can get started by then running feast init -t elasticsearch.
Example
project: my_feature_repo
registry: data/registry.db
provider: local
online_store:
type: elasticsearch
host: ES_HOST
port: ES_PORT
user: ES_USERNAME
password: ES_PASSWORD
write_batch_size: 1000The full set of configuration options is available in ElasticsearchOnlineStoreConfig.
Functionality Matrix
write feature values to the online store
yes
read feature values from the online store
yes
update infrastructure (e.g. tables) in the online store
yes
teardown infrastructure (e.g. tables) in the online store
yes
generate a plan of infrastructure changes
no
support for on-demand transforms
yes
readable by Python SDK
yes
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 ttl (time to live) at retrieval
no
support for deleting expired data
no
collocated by feature view
yes
collocated by feature service
no
collocated by entity key
no
To compare this set of functionality against other online stores, please see the full functionality matrix.
Retrieving online document vectors
The ElasticSearch online store supports retrieving document vectors for a given list of entity keys. The document vectors are returned as a dictionary where the key is the entity key and the value is the document vector. The document vector is a dense vector of floats.
Indexing
Currently, the indexing mapping in the ElasticSearch online store is configured as:
And the online_read API mapping is configured as:
And the similarity search API mapping is configured as:
These APIs are subject to change in future versions of Feast to improve performance and usability.
Last updated
Was this helpful?