[Alpha] Local feature server

Warning: This is an experimental feature. It's intended for early testing and feedback, and could change without warnings in future releases.

To enable this feature, runfeast alpha enable python_feature_server

Overview

The local feature server is an HTTP endpoint that serves features with JSON I/O. This enables users to get features from Feast using any programming language that can make HTTP requests. A remote feature server on AWS Lambda is also available. A remote feature server on GCP Cloud Run is currently being developed.

CLI

There is a new CLI command that starts the server: feast serve. By default Feast uses port 6566; the port be overridden by a --port flag.

Example

Here's the local feature server usage example with the local template:

$ feast init feature_repo
Creating a new Feast repository in /home/tsotne/feast/feature_repo.

$ cd feature_repo

$ feast apply
Registered entity driver_id
Registered feature view driver_hourly_stats
Deploying infrastructure for driver_hourly_stats

$ feast materialize-incremental $(date +%Y-%m-%d)
Materializing 1 feature views to 2021-09-09 17:00:00-07:00 into the sqlite online store.

driver_hourly_stats from 2021-09-09 16:51:08-07:00 to 2021-09-09 17:00:00-07:00:
100%|████████████████████████████████████████████████████████████████| 5/5 [00:00<00:00, 295.24it/s]

$ feast serve
This is an experimental feature. It's intended for early testing and feedback, and could change without warnings in future releases.
INFO:     Started server process [8889]
09/10/2021 10:42:11 AM INFO:Started server process [8889]
INFO:     Waiting for application startup.
09/10/2021 10:42:11 AM INFO:Waiting for application startup.
INFO:     Application startup complete.
09/10/2021 10:42:11 AM INFO:Application startup complete.
INFO:     Uvicorn running on http://127.0.0.1:6566 (Press CTRL+C to quit)
09/10/2021 10:42:11 AM INFO:Uvicorn running on http://127.0.0.1:6566 (Press CTRL+C to quit)

After the server starts, we can execute cURL commands from another terminal tab:

$  curl -X POST \
  "http://localhost:6566/get-online-features" \
  -d '{
    "features": [
      "driver_hourly_stats:conv_rate",
      "driver_hourly_stats:acc_rate",
      "driver_hourly_stats:avg_daily_trips"
    ],
    "entities": {
      "driver_id": [1001, 1002, 1003]
    }
  }' | jq
{
  "field_values": [
    {
      "fields": {
        "driver_id": 1001,
        "conv_rate": 0.07427442818880081,
        "avg_daily_trips": 140,
        "acc_rate": 0.8625795245170593
      },
      "statuses": {
        "conv_rate": "PRESENT",
        "acc_rate": "PRESENT",
        "driver_id": "PRESENT",
        "avg_daily_trips": "PRESENT"
      }
    },
    {
      "fields": {
        "avg_daily_trips": 646,
        "acc_rate": 0.8026317954063416,
        "conv_rate": 0.41487279534339905,
        "driver_id": 1002
      },
      "statuses": {
        "driver_id": "PRESENT",
        "avg_daily_trips": "PRESENT",
        "conv_rate": "PRESENT",
        "acc_rate": "PRESENT"
      }
    },
    {
      "fields": {
        "avg_daily_trips": 671,
        "conv_rate": 0.4033895432949066,
        "driver_id": 1003,
        "acc_rate": 0.06059994176030159
      },
      "statuses": {
        "driver_id": "PRESENT",
        "conv_rate": "PRESENT",
        "avg_daily_trips": "PRESENT",
        "acc_rate": "PRESENT"
      }
    }
  ]
}

It's also possible to specify a feature service name instead of the list of features:

curl -X POST \
  "http://localhost:6566/get-online-features" \
  -d '{
    "feature_service": <feature-service-name>,
    "entities": {
      "driver_id": [1001, 1002, 1003]
    }
  }' | jq