docs/reference/feature-servers/offline-feature-server.md
The Offline feature server is an Apache Arrow Flight Server that uses the gRPC communication protocol to exchange data. This server wraps calls to existing offline store implementations and exposes interfaces as Arrow Flight endpoints.
There is a CLI command that starts the Offline feature server: feast serve_offline. By default, remote offline server uses port 8815, the port can be overridden with a --port flag.
See this for an example on how to run Feast on Kubernetes using the Operator.
The Offline feature server can be deployed with a slight modification of the FeatureStore CR -
apiVersion: feast.dev/v1
kind: FeatureStore
metadata:
name: sample-offline-server
spec:
feastProject: my_project
services:
offlineStore:
server: {}
More advanced FeatureStore CR examples can be found in the feast-operator samples directory.
The complete example can be found under remote-offline-store-example
Please see the detail how to configure offline store client remote-offline-store.md
The set of functionalities supported by remote offline stores is the same as those supported by offline stores with the SDK, which are described in detail here.
| Endpoint | Resource Type | Permission | Description |
|---|---|---|---|
| offline_write_batch | FeatureView | Write Offline | Write a batch of data to the offline store |
| write_logged_features | FeatureService | Write Offline | Write logged features to the offline store |
| persist | DataSource | Write Offline | Persist the result of a read in the offline store |
| get_historical_features | FeatureView | Read Offline | Retrieve historical features |
| pull_all_from_table_or_query | DataSource | Read Offline | Pull all data from a table or read it |
| pull_latest_from_table_or_query | DataSource | Read Offline | Pull the latest data from a table or read it |
Please refer the page for more details on how to configure authentication and authorization.