Automazione delle pipeline di dati in Snowflake
Emily Melhuish
Technical Curriculum Developer, Snowflake
Use case:

Tabelle esterne
CREATE EXTERNAL TABLE logistics.supplier_inventory
WITH LOCATION = @harbr_stage/inventory/
FILE_FORMAT = (TYPE = 'PARQUET')
AUTO_REFRESH = TRUE;
-- Query inventario partner
SELECT supplier_id,
COUNT(*) AS file_count,
SUM(quantity) AS total_units
FROM logistics.supplier_inventory
WHERE delivery_date >= '2024-01-01'
GROUP BY supplier_id;
Tabelle esterne
-- Query diretta, senza caricamento
SELECT * FROM
logistics.supplier_inventory
WHERE supplier_id = 'SUP-042';
Caricamento con COPY INTO
-- Carica una volta, query veloci
COPY INTO logistics.delivery_events
FROM @harbr_stage/events/;
Come garantire una lettura corretta da S3, Azure Blob o GCS?
Apache = formato di tabella aperto: dati non vincolati a un motore

Gestite da Snowflake
CREATE ICEBERG TABLE
logistics.shipments
CATALOG = 'SNOWFLAKE'
EXTERNAL_VOLUME = 'harbr_s3_vol'
BASE_LOCATION = 'iceberg/shipments/';
Gestite esternamente
CREATE ICEBERG TABLE
logistics.partner_data
CATALOG = 'glue_catalog'
EXTERNAL_VOLUME = 'harbr_s3_vol'
CATALOG_TABLE_NAME =
'partner.deliveries';
Automazione delle pipeline di dati in Snowflake