### Query Documentation API Example

Source: https://docs.feast.dev/untitled/reference/data-sources/snowflake

This example shows how to query the documentation dynamically using an HTTP GET request with the 'ask' query parameter.

```bash
GET https://docs.feast.dev/untitled/reference/data-sources/snowflake.md?ask=<question>
```

--------------------------------

### Start and Create Redis Cluster

Source: https://docs.feast.dev/how-to-guides/adding-or-reusing-tests

Use these commands to start the Redis cluster and then create it. Ensure Redis is installed and the script is executable.

```bash
./infra/scripts/redis-cluster.sh start
./infra/scripts/redis-cluster.sh create
```

--------------------------------

### Query Documentation API Example

Source: https://docs.feast.dev/untitled/reference/data-sources/bigquery

Demonstrates how to query the documentation dynamically using an HTTP GET request with the `ask` query parameter.

```http
GET https://docs.feast.dev/untitled/reference/data-sources/bigquery.md?ask=<question>
```

--------------------------------

### Agent Instructions for Querying Documentation

Source: https://docs.feast.dev/reference/feature-repository/feast-ignore

This example demonstrates how to query the documentation dynamically using an HTTP GET request with the `ask` query parameter. This is useful for retrieving specific information not explicitly present on the page.

```http
GET https://docs.feast.dev/reference/feature-repository/feast-ignore.md?ask=<question>
```

--------------------------------

### Example GET Request with 'ask' Parameter

Source: https://docs.feast.dev/untitled/reference/batch-materialization/lambda

Demonstrates how to query the documentation dynamically by appending an 'ask' query parameter to the page URL. This is useful for retrieving specific information not explicitly present on the page.

```http
GET https://docs.feast.dev/untitled/reference/batch-materialization/lambda.md?ask=<question>
```

--------------------------------

### Query Documentation Dynamically

Source: https://docs.feast.dev/reference/data-sources/snowflake

This example shows how to programmatically query the documentation using a GET request with an 'ask' parameter. This is useful for retrieving specific information not immediately apparent in the documentation.

```bash
GET https://docs.feast.dev/reference/data-sources/snowflake.md?ask=<question>
```

--------------------------------

### Navigate to Example Directory

Source: https://docs.feast.dev/tutorials/mcp_feature_store

Navigate to the MCP feature store example directory within your cloned Feast repository.

```bash
cd examples/mcp_feature_store
```

--------------------------------

### Install Feast with Online Store Dependencies

Source: https://docs.feast.dev/reference/online-stores/hybrid

Install Feast with the necessary online store dependencies for the backends you plan to use. For example, to use Bigtable and Cassandra, install with `feast[gcp,cassandra]`.

```bash
pip install 'feast[gcp,cassandra]'
```

--------------------------------

### Start React App

Source: https://docs.feast.dev/untitled/reference/alpha-web-ui

Command to start the React development server after integrating Feast UI.

```bash
yarn start
```

--------------------------------

### Install Feast with Redis Extra

Source: https://docs.feast.dev/untitled/reference/online-stores/redis

Install the redis extra along with the dependency for your chosen offline store. Examples include GCP, Snowflake, AWS, and Azure.

```bash
pip install 'feast[gcp, redis]'
```

```bash
pip install 'feast[snowflake, redis]'
```

```bash
pip install 'feast[aws, redis]'
```

```bash
pip install 'feast[azure, redis]'
```

--------------------------------

### Install Feast with Offline Store Dependencies

Source: https://docs.feast.dev/reference/offline-stores/hybrid

Install Feast with all required offline store dependencies for the stores you plan to use. This example installs support for Spark and Snowflake.

```bash
pip install 'feast[spark,snowflake]'
```

--------------------------------

### Registry Server Configuration Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example configuration for the Feast Registry Server, showing how to define projects and relationships.

```json
{
    "projects": [
      {
        "name": "project1", 
        "registry_store": {
          "type": "local",
          "path": "/path/to/registry.db"
        },
        "relationships": [ ... ],
        "indirectRelationships": [ ... ]
      },
      { "project": "project2", ... }
    ]
  }
```

--------------------------------

### Query Documentation Dynamically

Source: https://docs.feast.dev/untitled/reference/data-sources/redshift

This example demonstrates how to query the Feast documentation dynamically for Redshift data sources by making an HTTP GET request with an 'ask' query parameter.

```bash
GET https://docs.feast.dev/untitled/reference/data-sources/redshift.md?ask=<question>
```

--------------------------------

### Install Base Feast

Source: https://docs.feast.dev/how-to-guides/feast-snowflake-gcp-aws/install-feast

Install the core Feast package using pip. This is the basic installation for Feast.

```bash
pip install feast
```

--------------------------------

### Install Feast SDK and CLI

Source: https://docs.feast.dev/reference/online-stores/dragonfly

Install the Feast SDK and CLI using pip. To use Dragonfly as an online store, you need to install the 'redis' extra.

```bash
pip install feast
```

```bash
pip install 'feast[redis]'
```

--------------------------------

### Install Denormalized and Feast

Source: https://docs.feast.dev/reference/denormalized

Install the necessary libraries for Denormalized with Feast integration. Ensure you are in a Python virtual environment.

```bash
pip install denormalized[feast] feast
```

--------------------------------

### Example Feast Configuration

Source: https://docs.feast.dev/reference/feast-cli-commands

An example of the configuration output from the `feast configuration` command, showing project, registry, provider, and store settings.

```yaml
project: foo
registry: data/registry.db
provider: local
online_store:
    type: sqlite
    path: data/online_store.db
offline_store: 
    type: dask 
entity_key_serialization_version: 3
auth:
    type: no_auth
```

--------------------------------

### Install Feast with Cassandra Support

Source: https://docs.feast.dev/reference/online-stores/scylladb

Install Feast with the necessary dependencies for Cassandra support. This command installs the core Feast library along with the Cassandra integration.

```bash
pip install "feast[cassandra]"
```

--------------------------------

### Example Usage Configuration

Source: https://docs.feast.dev/getting-started/components/open-telemetry

Example configuration snippet showing how to enable metrics and set the OpenTelemetry Collector endpoint in your Helm values.

```yaml
metrics:
  enabled: true
  otelCollector:
    endpoint: "otel-collector.default.svc.cluster.local:4317"
```

--------------------------------

### Resource Counts Response Example (Single Project)

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response when requesting resource counts for a single project.

```json
{
  "project": "my_project",
  "counts": {
    "entities": 5,
    "dataSources": 3,
    "savedDatasets": 2,
    "features": 12,
    "featureViews": 4,
    "featureServices": 2
  }
}
```

--------------------------------

### Platform Object Naming Convention Example

Source: https://docs.feast.dev/how-to-guides/feast-snowflake-gcp-aws/federated-feature-store

Example demonstrating a simple naming convention for platform-managed objects to prevent collisions.

```python
# Platform objects: simple names
user_features = FeatureView(name="user_features", ...)
```

--------------------------------

### Initialize and Serve Feature Repo

Source: https://docs.feast.dev/reference/feature-servers/python-feature-server

Demonstrates the steps to initialize a feature repository, apply configurations, materialize data, and start the feature server.

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

$ cd feature_repo

$ feast apply
Created entity driver
Created feature view driver_hourly_stats
Created feature service driver_activity

Created sqlite table feature_repo_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
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)
```

--------------------------------

### Get Object Relationships Response Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response for the 'Get Object Relationships' endpoint, detailing the source and target of relationships for a given object.

```json
{
  "relationships": [
    { "source": { "type": "feature", "name": "conv_rate" }, "target": { "type": "featureView", "name": "driver_hourly_stats_fresh" } },
    { "source": { "type": "feature", "name": "conv_rate" }, "target": { "type": "featureView", "name": "driver_hourly_stats" } }
  ],
  "pagination": { "totalCount": 2, "totalPages": 1 }
}
```

--------------------------------

### Get Registry Lineage (All Projects) Response Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response for the 'Get Registry Lineage (All Projects)' endpoint, showing relationships and indirect relationships with project context.

```json
{
  "relationships": [ { ... , "project": "project1" }, ... ],
  "indirect_relationships": [ { ... , "project": "project2" }, ... ]
}
```

--------------------------------

### Get Complete Registry Data Response Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response structure for the 'Get Complete Registry Data' endpoint, showing project details, objects, relationships, and pagination.

```json
{
  "project": "multiproject",
  "objects": {
    "entities": [ ... ],
    "dataSources": [ ... ],
    "featureViews": [ ... ],
    "featureServices": [ ... ],
    "features": [
      { "name": "conv_rate", "featureView": "driver_hourly_stats_fresh", "type": "Float32" },
      { "name": "acc_rate", "featureView": "driver_hourly_stats_fresh", "type": "Float32" },
      { "name": "avg_daily_trips", "featureView": "driver_hourly_stats_fresh", "type": "Int64" },
      { "name": "conv_rate", "featureView": "driver_hourly_stats", "type": "Float32" },
      { "name": "acc_rate", "featureView": "driver_hourly_stats", "type": "Float32" },
      { "name": "conv_rate_plus_val1", "featureView": "transformed_conv_rate_fresh", "type": "Float64" },
      { "name": "conv_rate_plus_val2", "featureView": "transformed_conv_rate_fresh", "type": "Float64" },
      { "name": "conv_rate_plus_val1", "featureView": "transformed_conv_rate", "type": "Float64" },
      { "name": "conv_rate_plus_val2", "featureView": "transformed_conv_rate", "type": "Float64" }
    ]
  },
  "relationships": [ ... ],
  "indirectRelationships": [ ... ],
  "pagination": {
    "features": { "totalCount": 10, "totalPages": 1 },
    ...
  }
}
```

--------------------------------

### Example feature_store.yaml Configuration

Source: https://docs.feast.dev/reference/feature-repository/feature-store-yaml

This is a basic example of a feature_store.yaml file. It specifies the project name, registry location, provider, and online store configuration.

```yaml
project: loyal_spider
registry: data/registry.db
provider: local
online_store:
    type: sqlite
    path: data/online_store.db
```

--------------------------------

### Feast UI Server Output

Source: https://docs.feast.dev/untitled/getting-started/quickstart

This is an example of the output you might see when the Feast UI server starts. It indicates the server process has started and is running on a specific port.

```bash
INFO:     Started server process [66664]
08/17/2022 01:25:49 PM uvicorn.error INFO: Started server process [66664]
INFO:     Waiting for application startup.
08/17/2022 01:25:49 PM uvicorn.error INFO: Waiting for application startup.
INFO:     Application startup complete.
08/17/2022 01:25:49 PM uvicorn.error INFO: Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8888 (Press CTRL+C to quit)
08/17/2022 01:25:49 PM uvicorn.error INFO: Uvicorn running on http://0.0.0.0:8888 (Press CTRL+C to quit)
```

--------------------------------

### Query Go Feature Server with 'ask' parameter

Source: https://docs.feast.dev/reference/feature-servers/go-feature-server

Demonstrates how to query documentation dynamically by appending an 'ask' query parameter to the URL. The question should be specific and self-contained.

```http
GET https://docs.feast.dev/reference/feature-servers/go-feature-server.md?ask=<question>
```

--------------------------------

### Feast UI Server TLS Mode Output

Source: https://docs.feast.dev/how-to-guides/starting-feast-servers-tls-mode

Example output indicating that the Feast UI server has started successfully in HTTPS mode.

```text
INFO:     Started server process [78872]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on https://0.0.0.0:8888 (Press CTRL+C to quit)
```

--------------------------------

### Bootstrap a New Feast Project

Source: https://docs.feast.dev/getting-started/quickstart

Use the `feast init` command to create a new feature repository. Navigate into the created directory to begin configuration.

```bash
feast init my_project
cd my_project/feature_repo
```

--------------------------------

### Example Integration Test with Feast

Source: https://docs.feast.dev/untitled/how-to-guides/adding-or-reusing-tests

This example demonstrates a typical integration test for Feast, showcasing the setup of feature views, feature services, and the retrieval of historical features. It utilizes pytest fixtures and parametrization for comprehensive testing across different environments and configurations.

```python
@pytest.mark.integration
@pytest.mark.universal_offline_stores
@pytest.mark.parametrize("full_feature_names", [True, False], ids=lambda v: f"full:{v}")
def test_historical_features(environment, universal_data_sources, full_feature_names):
    store = environment.feature_store

    (entities, datasets, data_sources) = universal_data_sources

    feature_views = construct_universal_feature_views(data_sources)

    entity_df_with_request_data = datasets.entity_df.copy(deep=True)
    entity_df_with_request_data["val_to_add"] = [
        i for i in range(len(entity_df_with_request_data))
    ]
    entity_df_with_request_data["driver_age"] = [
        i + 100 for i in range(len(entity_df_with_request_data))
    ]

    feature_service = FeatureService(
        name="convrate_plus100",
        features=[feature_views.driver ["conv_rate"]], feature_views.driver_odfv],
    )
    feature_service_entity_mapping = FeatureService(
        name="entity_mapping",
        features=[
            feature_views.location.with_name("origin").with_join_key_map(
                {"location_id": "origin_id"}
            ),
            feature_views.location.with_name("destination").with_join_key_map(
                {"location_id": "destination_id"}
            ),
        ],
    )

    store.apply(
        [
            driver(),
            customer(),
            location(),
            feature_service,
            feature_service_entity_mapping,
            *feature_views.values(),
        ]
    )
    # ... more test code

    job_from_df = store.get_historical_features(
        entity_df=entity_df_with_request_data,
        features=[
            "driver_stats:conv_rate",
            "driver_stats:avg_daily_trips",
            "customer_profile:current_balance",
            "customer_profile:avg_passenger_count",
            "customer_profile:lifetime_trip_count",
            "conv_rate_plus_100:conv_rate_plus_100",
            "conv_rate_plus_100:conv_rate_plus_100_rounded",
            "conv_rate_plus_100:conv_rate_plus_val_to_add",
            "order:order_is_success",
            "global_stats:num_rides",
            "global_stats:avg_ride_length",
            "field_mapping:feature_name",
        ],
        full_feature_names=full_feature_names,
    )

    if job_from_df.supports_remote_storage_export():
        files = job_from_df.to_remote_storage()
        print(files)
        assert len(files) > 0  # This test should be way more detailed

    start_time = datetime.utcnow()
    actual_df_from_df_entities = job_from_df.to_df()
    # ... more test code

    validate_dataframes(
        expected_df,
        table_from_df_entities,
        sort_by=[event_timestamp, "order_id", "driver_id", "customer_id"],
        event_timestamp = event_timestamp,
    )
    # ... more test code

```

--------------------------------

### Initialize Feast Project with Ray Template

Source: https://docs.feast.dev/reference/offline-stores/ray

Use the feast init command with the ray template to quickly set up a new Feast project with pre-configured Ray offline store and compute engine.

```bash
feast init -t ray my_ray_project
cd my_ray_project/feature_repo
```

--------------------------------

### Configure Local Registry

Source: https://docs.feast.dev/reference/registries/local

Example of how to configure the local registry in feature_store.yaml. This setup is intended for experimentation and specifies the registry path and offline store type.

```yaml
project: feast_local
registry:
  path: registry.pb
  cache_ttl_seconds: 60
online_store: null
offline_store:
  type: dask
```

--------------------------------

### Retrieve Online Features

Source: https://docs.feast.dev/reference/beta-on-demand-feature-view

Get online features by referencing individual features or using a feature service. This example shows how to retrieve features for a given entity row.

```python
entity_rows = [
    {
        "driver_id": 1001,
        "val_to_add": 1,
        "val_to_add_2": 2,
    }
]

online_response = store.get_online_features(
    entity_rows=entity_rows,
    features=[
        "driver_hourly_stats:conv_rate",
        "driver_hourly_stats:acc_rate",
        "transformed_conv_rate_python:conv_rate_plus_val1_python",
        "transformed_conv_rate_python:conv_rate_plus_val2_python",
        "transformed_conv_rate_singleton:conv_rate_plus_acc_singleton",
    ],
).to_dict()
```

--------------------------------

### Show Feast UI Help

Source: https://docs.feast.dev/reference/alpha-web-ui

Run this command in your feature repository to display help information for the `feast ui` command, including available options for host, port, and registry refresh.

```bash
Usage: feast ui [OPTIONS]

Shows the Feast UI over the current directory

Options:
-h, --host TEXT                 Specify a host for the server [default: 0.0.0.0]
-p, --port INTEGER              Specify a port for the server [default: 8888]
-r, --registry_ttl_sec INTEGER  Number of seconds after which the registry is refreshed. Default is 5 seconds.
--help                          Show this message and exit.
```

--------------------------------

### Search API Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Demonstrates the structure of a search query to the Registry Server API.

```json
{
    "query": "user",
    "projects_searched": ["existing_project"],
    "results": [],
    "pagination": {
      "page": 1,
      "limit": 50,
      "totalCount": 0,
      "totalPages": 0
    },
    "errors": []
  }
```

--------------------------------

### HTTP GET Request Example

Source: https://docs.feast.dev/untitled/getting-started/concepts/entity

Demonstrates how to query Feast documentation dynamically by appending an 'ask' query parameter to the URL. This is useful for retrieving specific information or clarifications not explicitly present on the page.

```http
GET https://docs.feast.dev/untitled/getting-started/concepts/entity.md?ask=<question>
```

--------------------------------

### Get Online Features with Feast SDK

Source: https://docs.feast.dev/how-to-guides/online-server-performance-tuning

Example of retrieving online features using the Feast SDK. This method involves registry lookup, proto conversion, HTTP POST, and JSON parsing.

```python
features = store.get_online_features(
    features=["driver_stats:conv_rate", "driver_stats:acc_rate"],
    entity_rows=[{"driver_id": 1001}, {"driver_id": 1002}],
)
```

--------------------------------

### Navigate to Feature Repository Directory

Source: https://docs.feast.dev/how-to-guides/feast-snowflake-gcp-aws/create-a-feature-repository

After initializing a feature repository, navigate into the newly created directory to begin development.

```bash
# Replace "tiny_pika" with your auto-generated dir name
cd tiny_pika
```

--------------------------------

### Feast Offline Server TLS Mode Output

Source: https://docs.feast.dev/how-to-guides/starting-feast-servers-tls-mode

Example output when the Feast offline server starts successfully in TLS mode, indicating the use of SSL certificates and the secure server URL.

```text
11/07/2024 11:10:01 AM feast.offline_server INFO: Found SSL certificates in the args so going to start offline server in TLS(SSL) mode.
11/07/2024 11:10:01 AM feast.offline_server INFO: Offline store server serving at: grpc+tls://127.0.0.1:8815
11/07/2024 11:10:01 AM feast.offline_server INFO: offline server starting with pid: [11606]
```

--------------------------------

### Define Project and Entities

Source: https://docs.feast.dev/getting-started/quickstart

Set up your project and define core entities like 'driver' which will be used as join keys for features. Ensure entity names are unique within the project.

```python
# Define a project for the feature repo
project = Project(name="my_project", description="A project for driver statistics")


# Define an entity for the driver. You can think of an entity as a primary key used to
# fetch features.
driver = Entity(name="driver", join_keys=["driver_id"])
```

--------------------------------

### List All Resources with Filtering

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Perform a search with an empty query string to retrieve all resources within specified projects, combined with pagination and filtering.

```bash
curl -H "Authorization: Bearer <token>" \
  "http://localhost:6572/api/v1/search?query=&projects=my_project&page=1&limit=20"
```

--------------------------------

### Apply Feature Store Configuration

Source: https://docs.feast.dev/tutorials/mcp_feature_store

Navigate to the feature_repo directory and apply the feature store configuration.

```bash
cd feature_repo 
feast apply
cd .. # Go back to examples/mcp_feature_store for the next steps
```

--------------------------------

### Install Feast with dbt support

Source: https://docs.feast.dev/how-to-guides/dbt-integration

Install Feast with the dbt integration package or install the dbt artifacts parser directly.

```bash
pip install 'feast[dbt]'
```

```bash
pip install dbt-artifacts-parser
```

--------------------------------

### Resource Counts Response Example (All Projects)

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response when requesting resource counts for all projects, showing total counts and per-project breakdowns.

```json
{
  "total": {
    "entities": 15,
    "dataSources": 8,
    "savedDatasets": 5,
    "features": 35,
    "featureViews": 12,
    "featureServices": 6
  },
  "perProject": {
    "project_a": {
      "entities": 5,
      "dataSources": 3,
      "savedDatasets": 2,
      "features": 12,
      "featureViews": 4,
      "featureServices": 2
    },
    "project_b": {
      "entities": 10,
      "dataSources": 5,
      "savedDatasets": 3,
      "features": 23,
      "featureViews": 8,
      "featureServices": 4
    }
  }
}
```

--------------------------------

### Instantiate FeatureStore with repo_path

Source: https://docs.feast.dev/getting-started/components/registry

Instantiate a `FeatureStore` object by providing the repository path, which will load the configuration from `feature_store.yaml`.

```python
store = FeatureStore(repo_path=".")
```

--------------------------------

### Initialize Feature Store and Serve Transformations (Python)

Source: https://docs.feast.dev/reference/feature-servers/go-feature-server

Use this Python code to initialize a Feast FeatureStore and start the transformation server. Ensure the port matches the configuration in `feature_store.yaml`.

```python
# -*- coding: utf-8 -*-
from feast.feature_store import FeatureStore


def main():
    # Init the Feature Store
    store = FeatureStore(repo_path="./feature_repo/")

    # Start the feature transformation server
    # default port is 6569
    store.serve_transformations(6569)

if __name__ == "__main__":
    main()
```

--------------------------------

### Install Pre-commit Hooks

Source: https://docs.feast.dev/project/development-guide

Installs pre-commit and its associated hooks to automatically lint and format the codebase on commit. Ensure Python 3.10+ and uv are installed first.

```sh
make install-precommit
```

--------------------------------

### Install MCP Support with Feast

Source: https://docs.feast.dev/getting-started/genai

Install Feast with MCP support using pip. This command installs the necessary libraries for enabling Model Context Protocol integration.

```bash
pip install feast[mcp]
```

--------------------------------

### Initialize Feast Repository with Template

Source: https://docs.feast.dev/untitled/reference/feast-cli-commands

Initializes a new Feast repository using a specific template, such as the 'gcp' template.

```bash
feast init -t gcp my_feature_repo
```

--------------------------------

### Querying Documentation with GET Request

Source: https://docs.feast.dev/reference/online-stores/dynamodb

To get additional information not explicitly on the page, make a GET request to the page URL with an `ask` query parameter containing your question.

```http
GET https://docs.feast.dev/reference/online-stores/dynamodb.md?ask=<question>
```

--------------------------------

### Build and Install Feast Python Feature Server with Helm

Source: https://docs.feast.dev/project/development-guide

Builds a local Python feature server binary and installs the local Helm chart. Requires `minikube` for local testing. The `feature_store_yaml_base64` parameter expects a base64 encoded feature store configuration.

```bash
make build-feature-server-dev
```

```bash
helm install feast-release ../../../infra/charts/feast-feature-server --set image.tag=dev --set feature_store_yaml_base64=$(base64 feature_store.yaml)
```

--------------------------------

### Response Example for All Feature Views

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response structure when listing all feature views across projects, including pagination details.

```json
{
  "featureViews": [
    { "name": "user_features", "project": "project1", ... },
    { "name": "item_features", "project": "project2", ... }
  ],
  "pagination": { "page": 1, "limit": 10, "total": 25, "totalPages": 3 },
  "relationships": { ... }
}
```

--------------------------------

### Querying Documentation with GET Request

Source: https://docs.feast.dev/untitled/reference/offline-stores/file

To get additional information not directly present on the page, perform an HTTP GET request with the 'ask' query parameter. The question should be specific and self-contained.

```http
GET https://docs.feast.dev/untitled/reference/offline-stores/file.md?ask=<question>
```

--------------------------------

### Registry Server Modes

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Examples of how to run the Feast Registry Server in different modes.

```bash
feast serve_registry
```

```bash
feast serve_registry --rest-api
```

```bash
feast serve_registry --rest-api --no-grpc
```

--------------------------------

### Query Documentation via HTTP GET

Source: https://docs.feast.dev/untitled/how-to-guides/feast-snowflake-gcp-aws/deploy-a-feature-store

To get information not explicitly on the page, make an HTTP GET request to the page URL with an `ask` query parameter containing your question.

```http
GET https://docs.feast.dev/untitled/how-to-guides/feast-snowflake-gcp-aws/deploy-a-feature-store.md?ask=<question>
```

--------------------------------

### Start Registry Server in TLS Mode

Source: https://docs.feast.dev/reference/feature-servers/registry-server

To start the Registry Server in TLS mode, you must provide the private key and public certificate paths using the `--key` and `--cert` arguments respectively. This ensures secure communication.

```bash
feast serve_registry --key path/to/private.key --cert path/to/public.crt
```

--------------------------------

### Install Python with SQLite Extensions

Source: https://docs.feast.dev/reference/alpha-vector-database

Configures and installs a specific Python version (3.10.14) with SQLite loadable extensions enabled, often used with pyenv. This is a prerequisite for installing Feast with SQLite support.

```bash
PYTHON_CONFIGURE_OPTS="--enable-loadable-sqlite-extensions" \
    LDFLAGS="-L/opt/homebrew/opt/sqlite/lib" \
    CPPFLAGS="-I/opt/homebrew/opt/sqlite/include" \
    pyenv install 3.10.14
```

--------------------------------

### Querying Documentation via HTTP GET

Source: https://docs.feast.dev/reference/providers/amazon-web-services

To get additional information not directly present on the page, perform an HTTP GET request to the page URL with an 'ask' query parameter containing your question.

```http
GET https://docs.feast.dev/reference/providers/amazon-web-services.md?ask=<question>
```

--------------------------------

### Build Go feature server from source

Source: https://docs.feast.dev/untitled/reference/feature-servers/go-feature-server

Developers can build the Go feature server from source using `make compile-go-lib`. This command requires the Apache Arrow C++ libraries to be installed.

```bash
make compile-go-lib
```

--------------------------------

### Querying Documentation via HTTP GET

Source: https://docs.feast.dev/reference/offline-stores/redshift

To get additional information not directly on the page, perform an HTTP GET request to the current page URL with the 'ask' query parameter. The question should be specific and self-contained.

```http
GET https://docs.feast.dev/reference/offline-stores/redshift.md?ask=<question>
```

--------------------------------

### Query Documentation Dynamically

Source: https://docs.feast.dev/reference/offline-stores/ray

Perform an HTTP GET request on the current page URL with the `ask` query parameter to get specific information or clarifications from the documentation.

```bash
GET https://docs.feast.dev/reference/offline-stores/ray.md?ask=<question>
```

--------------------------------

### Feature Services Response Example

Source: https://docs.feast.dev/reference/feature-servers/registry-server

Example JSON response structure for listing feature services.

```json
{
  "featureServices": [
    { "name": "recommendation_service", "project": "project1", ... },
    { "name": "scoring_service", "project": "project2", ... }
  ],
  "pagination": { "page": 1, "limit": 10, "total": 25, "totalPages": 3 },
  "relationships": { ... }
}
```

--------------------------------

### Query Documentation Dynamically

Source: https://docs.feast.dev/how-to-guides/feast-snowflake-gcp-aws/federated-feature-store

Perform an HTTP GET request on the current page URL with the `ask` query parameter to dynamically query documentation. The question should be specific and self-contained. The response will contain a direct answer and relevant excerpts.

```bash
GET https://docs.feast.dev/how-to-guides/feast-snowflake-gcp-aws/federated-feature-store.md?ask=<question>
```

--------------------------------

### Install OpenLineage Dependency

Source: https://docs.feast.dev/reference/openlineage

Install the OpenLineage Python package or Feast with the OpenLineage extra to enable integration.

```bash
pip install openlineage-python
```

```bash
pip install feast[openlineage]
```