Serialization version 2 and below removed

Signed-off-by: jyejare <[email protected]>

Author: jyejare

docs/getting-started/quickstart.md

@@ -113,7 +113,7 @@ provider: local
 online_store:
   type: sqlite
   path: data/online_store.db
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 ```
 {% endtab %}
 

docs/how-to-guides/entity-reserialization-of-from-v2-to-v3.md

@@ -1,16 +1,16 @@
-# Entity Key Re-Serialization from Version 2 to 3
+# Entity Key Serialization from Version 2 to Version 3
 
-Entity Key Serialization version 2 will soon be deprecated, hence we need to shift the serialization and deserilization to version 3. 
+Entity Key Serialization version 2 is now deprecated. All new and existing Feast deployments should shift to using serialization version 3.
 
-But here comes the challegnge where existing FeatuteViews on stores has written features with version 2. A version 2 serialized entity key cant be retrived using version 3 deserilization algorithm.
+However, a challenge arises when existing FeatureViews in online or offline stores have written features with version 2. A version 2 serialized entity key cannot be retrieved using the version 3 deserialization algorithm.
 
 ## Reserialize the Feature Views entity Keys to version 3
 
 The solution is to reserialize the entity keys from version 2 to version 3.
 
 Follow the following procedures to reserialize the entity key to version 3 in feature View in an offline / online store.
 
-In hosrt, you need to iterate through all the feature views in your Feast repository, retrieve their serialized entity keys (if stored in version 2), reserialize them to version 3, and then update the online/offline store or wherever the serialized keys are stored.
+In short, you need to iterate through all the feature views in your Feast repository, retrieve their serialized entity keys (if stored in version 2), reserialize them to version 3, and then update the online/offline store or wherever the serialized keys are stored.
 
 ### 1. Initialize the Feature Store
 

docs/how-to-guides/running-feast-in-production.md

@@ -88,7 +88,7 @@ def materialize(data_interval_start=None, data_interval_end=None):
     provider="aws",
     offline_store="file",
     online_store=DynamoDBOnlineStoreConfig(region="us-west-2"),
-    entity_key_serialization_version=2
+    entity_key_serialization_version=3
   )
   store = FeatureStore(config=repo_config)
   # Option 1: materialize just one feature view

docs/how-to-guides/starting-feast-servers-tls-mode.md

@@ -83,7 +83,7 @@ online_store:
   path: http://localhost:6566
   type: remote
   cert: /path/to/cert.pem
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 auth:
   type: no_auth
 ```
@@ -121,7 +121,7 @@ online_store:
   path: http://localhost:6566
   type: remote
   cert: /path/to/cert.pem
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 auth:
   type: no_auth
 ```
@@ -161,7 +161,7 @@ online_store:
   path: http://localhost:6566
   type: remote
   cert: /path/to/cert.pem
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 offline_store:
   type: remote
   host: localhost

docs/reference/batch-materialization/spark.md

@@ -47,7 +47,7 @@ repo_config = RepoConfig(
       "partitions": 10
     },
     online_store=DynamoDBOnlineStoreConfig(region="us-west-1"),
-    entity_key_serialization_version=2
+    entity_key_serialization_version=3
 )
 
 store = FeatureStore(config=repo_config)

docs/reference/feast-cli-commands.md

@@ -79,7 +79,7 @@ online_store:
     path: data/online_store.db
 offline_store: 
     type: dask 
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 auth:
     type: no_auth
 ```

docs/reference/online-stores/couchbase.md

@@ -44,7 +44,7 @@ online_store:
   password: password  # Couchbase password from access credentials
   bucket_name: feast  # Couchbase bucket name, defaults to feast
   kv_port: 11210  # Couchbase key-value port, defaults to 11210. Required if custom ports are used. 
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 ```
 {% endcode %}
 

docs/reference/online-stores/remote.md

@@ -17,7 +17,7 @@ online_store:
   path: http://localhost:6566
   type: remote
   cert: /path/to/cert.pem
-entity_key_serialization_version: 2
+entity_key_serialization_version: 3
 auth:
   type: no_auth
 ```

examples/java-demo/README.md

@@ -1,4 +1,3 @@
-
 # Running Feast Java Server with Redis & calling with python (with registry in GCP)
 
 For this tutorial, we setup Feast with Redis, using the Feast CLI to register and materialize features, and then retrieving via a Feast Java server deployed in Kubernetes via a gRPC call.
@@ -40,7 +39,7 @@ For this tutorial, we setup Feast with Redis, using the Feast CLI to register an
       connection_string: localhost:6379,password=[YOUR PASSWORD]
     offline_store:
       type: file
-    entity_key_serialization_version: 2
+    entity_key_serialization_version: 3
     ```
 4. Run `feast apply` to apply your local features to the remote registry
      - Note: you may need to authenticate to gcloud first with `gcloud auth login` 
@@ -86,7 +85,7 @@ For this tutorial, we setup Feast with Redis, using the Feast CLI to register an
    >2. `make build-java-docker-dev` 
    >3. In the `application-override.yaml`, uncomment the two `image: tag: dev` blocks 
    >4. `helm install feast-release ../../../infra/charts/feast --values application-override.yaml`
-5. (Optional): check logs of the server to make sure it’s working
+5. (Optional): check logs of the server to make sure it's working
    ```bash
    kubectl logs svc/feast-release-feature-server
    ```

examples/java-demo/feature_repo/application-override.yaml

@@ -10,7 +10,7 @@ feature-server:
                 host: my-redis-master
                 port: 6379
                 password: [YOUR PASSWORD]
-            entityKeySerializationVersion: 2
+            entityKeySerializationVersion: 3
     # Uncomment below for dev
 #    image:
 #      tag: dev