Skip to content

Commit 6cd3c82

Browse files
committed
Rewriting section to focus and clarify that Iceberg table is done with support assistance
1 parent 0c31daa commit 6cd3c82

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

content/shared/influxdb3-query-guides/snapshots/snowflake.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,17 +81,21 @@ After configuring the export settings in the `config.json` file, the system auto
8181
8282
### Create an Iceberg table in Snowflake
8383
84-
After exporting the data, create an Iceberg table in Snowflake.
84+
After the export process is complete, you'll work with your InfluxData support engineer to create an Iceberg table in Snowflake that references your exported data. Here's what happens during this step:
8585
86-
#### Example: Create an Iceberg table in Snowflake
86+
1. Your support engineer will provide you with the location of the Iceberg metadata file generated during the export process.
87+
88+
2. Using this information, you or your database administrator will execute a SQL command in Snowflake similar to:
8789
8890
```sql
8991
CREATE ICEBERG TABLE my_iceberg_table
9092
EXTERNAL_VOLUME = 'my_external_volume'
9193
METADATA_FILE_PATH = 's3://my-bucket/path/to/metadata.json';
9294
```
9395
94-
Ensure that `EXTERNAL_VOLUME` and `METADATA_FILE_PATH` point to your external storage and metadata file.
96+
3. Your support engineer will help ensure the EXTERNAL_VOLUME and METADATA_FILE_PATH parameters correctly point to your external storage and metadata file.
97+
98+
This creates a table in Snowflake that reads directly from the Iceberg-formatted data exported from your InfluxDB instance.
9599
96100
### Query the Iceberg table from Snowflake
97101

0 commit comments

Comments
 (0)