chore: Add documentation for custom offline stores

docs/how-to-guides/adding-a-new-offline-store.md

@@ -28,7 +28,8 @@ The OfflineStore class contains a couple of methods to read features from the of
 There are two methods that deal with reading data from the offline stores`get_historical_features`and `pull_latest_from_table_or_query`.
 
 * `pull_latest_from_table_or_query` is invoked when running materialization (using the `feast materialize` or `feast materialize-incremental` commands, or the corresponding `FeatureStore.materialize()` method. This method pull data from the offline store, and the `FeatureStore` class takes care of writing this data into the online store.
-* `get_historical_features `is invoked when reading values from the offline store using the `FeatureStore.get_historica_features()` method. Typically, this method is used to retrieve features when training ML models.
+* `get_historical_features` is invoked when reading values from the offline store using the `FeatureStore.get_historical_features()` method. Typically, this method is used to retrieve features when training ML models.
+* `pull_all_from_table_or_query` is a method that pulls all the data from an offline store from a specified start date to a specified end date.
 
 {% code title="feast_custom_offline_store/file.py" %}
 ```python
@@ -223,7 +224,7 @@ To use our custom file offline store, we can use the following `feature_store.ya
 project: test_custom
 registry: data/registry.db
 provider: local
-offline_store: 
+offline_store:
     type: feast_custom_offline_store.file.CustomFileOfflineStore
 ```
 {% endcode %}

sdk/python/feast/infra/offline_stores/offline_store.py

@@ -179,9 +179,24 @@ def pull_latest_from_table_or_query(
         end_date: datetime,
     ) -> RetrievalJob:
         """
+        This method pulls data from the offline store, and the FeatureStore class is used to write
+        this data into the online store. This method is invoked when running materialization (using
+        the `feast materialize` or `feast materialize-incremental` commands, or the corresponding
+        FeatureStore.materialize() method. This method pulls data from the offline store, and the FeatureStore
+        class is used to write this data into the online store.
+
         Note that join_key_columns, feature_name_columns, event_timestamp_column, and created_timestamp_column
         have all already been mapped to column names of the source table and those column names are the values passed
         into this function.
+
+        Args:
+            config: Repo configuration object
+            data_source: Data source to pull all of the columns from
+            join_key_columns: Columns of the join keys
+            feature_name_columns: Columns of the feature names needed
+            event_timestamp_column: Timestamp column
+            start_date: Starting date of query
+            end_date: Ending date of query
         """
         pass
 
@@ -210,8 +225,19 @@ def pull_all_from_table_or_query(
         end_date: datetime,
     ) -> RetrievalJob:
         """
+        Returns a Retrieval Job for all join key columns, feature name columns, and the event timestamp columns that occur between the start_date and end_date.
+
         Note that join_key_columns, feature_name_columns, event_timestamp_column, and created_timestamp_column
         have all already been mapped to column names of the source table and those column names are the values passed
         into this function.
+
+        Args:
+            config: Repo configuration object
+            data_source: Data source to pull all of the columns from
+            join_key_columns: Columns of the join keys
+            feature_name_columns: Columns of the feature names needed
+            event_timestamp_column: Timestamp column
+            start_date: Starting date of query
+            end_date: Ending date of query
         """
         pass