From 41201109d773559d21938ace37c832025811b768 Mon Sep 17 00:00:00 2001 From: Esteban Pastorino Date: Fri, 27 Sep 2024 15:02:35 +0100 Subject: [PATCH] More explicit mention about object storage pipes and MVs Be explicit about the permissions needed, or a workaround with roles. --- .../en/integrations/data-ingestion/clickpipes/object-storage.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/integrations/data-ingestion/clickpipes/object-storage.md b/docs/en/integrations/data-ingestion/clickpipes/object-storage.md index 384036391c5..bd129894641 100644 --- a/docs/en/integrations/data-ingestion/clickpipes/object-storage.md +++ b/docs/en/integrations/data-ingestion/clickpipes/object-storage.md @@ -96,6 +96,8 @@ To increase the throughput on large ingest jobs, we recommend scaling the ClickH ## Materialized Views +Object Storage ClickPipes with materialized views require `Full access` permissions to be selected when created. If this is not possible, ensure that the role used by the pipe can create tables and materialized views in the destination database. + Materialized views created while an Object Storage ClickPipe is running will not be populated. Stopping and restarting the pipe will cause the pipe to pick up the materialized views and start populating them. See [Limitations](#limitations) below. ## Limitations