Skip to content

Add some documentation on running feast-serving with feast 0.10 #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
achals merged 1 commit into from
Oct 21, 2021
Merged

Add some documentation on running feast-serving with feast 0.10 #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,15 @@ make build-docker REGISTRY=gcr.io/kf-feast VERSION=develop
```


#### IDE Setup
If you're using IntelliJ, some additional steps may be needed to make sure IntelliJ autocomplete works as expected.
Specifically, proto-generated code is not indexed by IntelliJ. To fix this, navigate to the following window in IntelliJ:
`Project Structure > Modules > datatypes-java`, and mark the following folders as `Source` directorys:
- target/generated-sources/protobuf/grpc-java
- target/generated-sources/protobuf/java
- target/generated-sources/annotations


## Feast Core
### Environment Setup
Setting up your development environment for Feast Core:
Expand Down
11 changes: 11 additions & 0 deletions serving/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,3 +88,14 @@ with open("/tmp/000000000000.avro", "rb") as f:
print(df.head(5))
EOF
```
#### Working with Feast 0.10+
Feast serving supports reading feature values materialized into Redis by feast 0.10+. To configure this, feast-serving
needs to be able to read the registry file for the project.
The location of the registry file can be specified in the `application.yml` like so:
```yaml
feast:
registry: "src/test/resources/docker-compose/feast10/registry.db"
```

This changes the behaviour of feast-serving to look up feature view definitions and specifications from the registry file instead
of the core service.