From c9eeebc920e9ecfb809154081031960452d44abe Mon Sep 17 00:00:00 2001 From: Anton Burnashev Date: Tue, 10 Sep 2024 17:29:45 +0200 Subject: [PATCH] Update docs/website/docs/tutorial/rest-api.md Co-authored-by: Akela Drissner-Schmid <32450038+akelad@users.noreply.github.com> --- docs/website/docs/tutorial/rest-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/website/docs/tutorial/rest-api.md b/docs/website/docs/tutorial/rest-api.md index 8608938eb9..4242fb36bb 100644 --- a/docs/website/docs/tutorial/rest-api.md +++ b/docs/website/docs/tutorial/rest-api.md @@ -254,7 +254,7 @@ pokemon_source = rest_api_source( ## Loading data incrementally -When working with some APIs, you may need to load data incrementally to avoid fetching the entire dataset every time and to reduce the load time. The API that support incremental loading usually provide a way to fetch only new or changed data (most often by using a timestamp field like `updated_at`, `created_at`, or incremental IDs). +When working with some APIs, you may need to load data incrementally to avoid fetching the entire dataset every time and to reduce the load time. APIs that support incremental loading usually provide a way to fetch only new or changed data (most often by using a timestamp field like `updated_at`, `created_at`, or incremental IDs). To illustrate incremental loading, let's consider the GitHub API. In the `rest_api_pipeline.py` file, you can find an example of how to load data from the GitHub API incrementally. Let's take a look at the configuration: