From 389b8b0f9d4f1ee35fb92e3b704b31d0cce972e3 Mon Sep 17 00:00:00 2001 From: Cody Lin Date: Fri, 15 Oct 2021 17:10:49 -0700 Subject: [PATCH] Improve the paragraph organization and make it clearer Signed-off-by: Cody Lin --- docs/getting-started/concepts/feature-view.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/concepts/feature-view.md b/docs/getting-started/concepts/feature-view.md index 343c8a1849..988f8140e7 100644 --- a/docs/getting-started/concepts/feature-view.md +++ b/docs/getting-started/concepts/feature-view.md @@ -55,7 +55,11 @@ global_stats_fv = FeatureView( ## Entity aliasing -"Entity aliases" can be specified to join `entity_df` columns that do not match the column names in the feature data table. Another use case involves entities that are a subclass of a more general entity. For example, "spammer" and "reporter" could be aliases of a "user" entity, and "origin" and "destination" could be aliases of a "location" entity as shown below. It is suggested that you dynamically specify the new FeatureView name using `.with_name` and `join_key_map` override using `.with_join_key_map` instead of register each new copy. +"Entity aliases" can be specified to join `entity_dataframe` columns that do not match the column names in the source table of a FeatureView. + +This could be used if a user has no control over these column names or if there are multiple entities are a subclass of a more general entity. For example, "spammer" and "reporter" could be aliases of a "user" entity, and "origin" and "destination" could be aliases of a "location" entity as shown below. + +It is suggested that you dynamically specify the new FeatureView name using `.with_name` and `join_key_map` override using `.with_join_key_map` instead of needing to register each new copy. {% tabs %} {% tab title="location_stats_feature_view.py" %}