Updated feature view documentation to include blurb about feature inferencing (#2096)

mavysavydav · web-flow · commit 39b6e7203428 · 2021-12-01T10:52:31.000-08:00
* Updated feature view documentation to include blurb about inferencing

Signed-off-by: David Y Liu &lt;davidyliuliu@gmail.com&gt;

* Updated according to CR comments

Signed-off-by: David Y Liu &lt;davidyliuliu@gmail.com&gt;
diff --git a/docs/getting-started/concepts/feature-view.md b/docs/getting-started/concepts/feature-view.md
@@ -53,6 +53,12 @@ global_stats_fv = FeatureView(
 {% endtab %}
 {% endtabs %}
 
+## Feature inferencing
+
+If the `features` parameter is not specified in the feature view creation, Feast will infer the features during `feast apply` by creating a feature for each column in the
+underlying data source except the columns corresponding to the entities of the feature view or the columns corresponding to the timestamp columns of the feature view's
+data source. The names and value types of the inferred features will use the names and data types of the columns from which the features were inferred.
+
 ## Entity aliasing
 
 "Entity aliases" can be specified to join `entity_dataframe` columns that do not match the column names in the source table of a FeatureView.
diff --git a/docs/reference/feature-repository/registration-inferencing.md b/docs/reference/feature-repository/registration-inferencing.md
@@ -0,0 +1,7 @@
+# Registration Inferencing
+
+## Overview
+
+* FeatureView - When the `features` parameter is left out of the feature view definition, upon a `feast apply` call, Feast will automatically consider every column in the data source as a feature to be registered other than the specific timestamp columns associated with the underlying data source definition (e.g. event_timestamp_column) and the columns associated with the feature view's entities.
+* DataSource - When the `event_timestamp_column` parameter is left out of the data source definition, upon a 'feast apply' call, Feast will automatically find the sole timestamp column in the table underlying the data source and use that as the `event_timestamp_column`. If there are no columns of timestamp type or multiple columns of timestamp type, `feast apply` will throw an exception.
+* Entity - When the `value_type` parameter is left out of the entity definition, upon a `feast apply` call, Feast will automatically find the column corresponding with the entity's `join_key` and take that column's data type to be the `value_type`. If the column doesn't exist, `feast apply` will throw an exception.
