build-feature-server-dev:

docker buildx build \

-t feastdev/feature-server:dev \

From a developer's perspective, there are three ways to push feature values to the online store with different tradeoffs.

This has two important consequences: (1) communication patterns between the Data Producer (i.e., the client) and Feast (i.e,. the server) and (2) feature computation and

_feature value_ write patterns to Feast's online store.

.PHONY: feast-ci-dev-docker-img

feast-ci-dev-docker-img:

.PHONY: docker-push

cassandra = ["cassandra-driver>=3.24.0,<4"]

couchbase = ["couchbase==4.3.2"]

delta = ["deltalake"]

duckdb = ["ibis-framework[duckdb]>=9.0.0,<10"]

elasticsearch = ["elasticsearch>=8.13.0"]

faiss = ["faiss-cpu>=1.7.0,<2"]

spark = ["pyspark>=3.0.0,<4"]

trino = ["trino>=0.305.0,<0.400.0", "regex"]

postgres = ["psycopg[binary,pool]>=3.0.0,<4"]

qdrant = ["qdrant-client>=1.12.0"]

redis = [

"redis>=4.2.2,<5",

"types-setuptools",

"types-tabulate",

"virtualenv<20.24.2",

]

dev = ["feast[ci]"]

docs = ["feast[ci]"]