From 6bceae80027e3072b6ad81474530d0a874d533ae Mon Sep 17 00:00:00 2001 From: Niels Bantilan Date: Tue, 4 Jan 2022 16:58:53 -0500 Subject: [PATCH] Update sqlite3_integration.py (#550) Signed-off-by: Niels Bantilan --- .../integrations/flytekit_plugins/sql/sqlite3_integration.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cookbook/integrations/flytekit_plugins/sql/sqlite3_integration.py b/cookbook/integrations/flytekit_plugins/sql/sqlite3_integration.py index f9b34ad3e2..88b60cdf46 100644 --- a/cookbook/integrations/flytekit_plugins/sql/sqlite3_integration.py +++ b/cookbook/integrations/flytekit_plugins/sql/sqlite3_integration.py @@ -6,8 +6,8 @@ The following example shows how you can write SQLite3 queries using the SQLite3Task, which is bundled as part of the core flytekit. Since SQL Queries are portable across workflows and Flyte installations (as long as the data exists), -this task will always run with a pre-built container, specifically the [flytekit container](https://github.com/flyteorg/flytekit/blob/v0.19.0/Dockerfile.py38) itself. -and thus users are not required to build a container for SQLite3. You can simply implement the task - register and +this task will always run with a pre-built container, specifically the `flytekit container `__ +itself. Therefore, users are not required to build a container for SQLite3. You can simply implement the task - register and execute it immediately. In some cases local execution is not possible - e.g. Snowflake. But for SQLlite3 local execution is also supported.