This reference describes how to configure Feast components:
Available configuration properties for Feast Core and Feast Online Serving can be referenced from the corresponding application.yml
of each component:
Configuration properties for Feast Core and Feast Online Serving are defined depending on Feast is deployed:
For each Feast component deployed using Docker Compose, configuration properties from application.yml
can be set at:
A reference of the sub-chart-specific configuration can found in its values.yml
:
Configuration properties can be set via application-override.yaml
for each component in values.yaml
:
If Feast is built and running from source, configuration properties can be set directly in the Feast component's application.yml
:
1. Command line arguments or initialized arguments: Passing parameters to the Feast CLI or instantiating the Feast Client object with specific parameters will take precedence above other parameters.
2. Environmental variables: Environmental variables can be set to provide configuration options. They must be prefixed with FEAST_
. For example FEAST_CORE_URL
.
3. Configuration file: Options with the lowest precedence are configured in the Feast configuration file. Feast looks for or creates this configuration file in ~/.feast/config
if it does not already exist. All options must be defined in the [general]
section of this file.
Visit the available configuration parameters for Feast Python SDK and Feast CLI to learn more.
The Feast Java SDK and Feast Go SDK are configured via arguments passed when instantiating the respective Clients:
Visit the Feast Go SDK API reference to learn more about available configuration parameters.
Visit the Feast Java SDK API reference to learn more about available configuration parameters.