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

achals · web-flow · commit 6a270106fcd9 · 2021-10-21T16:17:04.000-07:00
Signed-off-by: Achal Shah &lt;achals@gmail.com&gt;
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -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:
diff --git a/serving/README.md b/serving/README.md
@@ -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.
