Skip to content

Commit

Permalink
Improve the paragraph organization and make it clearer
Browse files Browse the repository at this point in the history
Signed-off-by: Cody Lin <[email protected]>
  • Loading branch information
Cody Lin committed Oct 16, 2021
1 parent ceba198 commit 389b8b0
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/getting-started/concepts/feature-view.md
Original file line number Diff line number Diff line change
Expand Up @@ -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" %}
Expand Down

0 comments on commit 389b8b0

Please sign in to comment.