Snowflake
Connect Snowflake to your preprocessing pipeline, and use the Unstructured Ingest CLI or the Unstructured Ingest Python library to batch process all your documents and store structured outputs locally on your filesystem.
The requirements are as follows.
-
A Snowflake account and its identifier.
-
The Snowflake username and its password in the account.
-
The Snowflake hostname and its port number in the account.
-
The name of the Snowflake database in the account.
-
The name of the schema in the database.
-
The name of the table in the schema.
Snowflake requires the target table to have a defined schema before Unstructured can write to the table. The recommended table schema for Unstructured is as follows:
SQL
The Snowflake connector dependencies:
You might also need to install additional dependencies, depending on your needs. Learn more.
These environment variables:
SNOWFLAKE_ACCOUNT
- The ID of the Snowflake account, represented by--account
(CLI) oraccount
(Python).SNOWFLAKE_USER
- The name of the Snowflake user, represented by--user
(CLI) oruser
(Python).SNOWFLAKE_PASSWORD
- The user’s password, represented by--password
(CLI) orpassword
(Python).SNOWFLAKE_HOST
- The hostname for the Snowflake account, represented by--host
(CLI) orhost
(Python).SNOWFLAKE_PORT
- The host’s port number, represented by--port
(CLI) orport
(Python).SNOWFLAKE_DATABASE
- The name of the Snowflake database, represented by--database
(CLI) ordatabase
(Python).
Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The destination connector can be any of the ones supported. This example uses the local destination connector:
This example sends data to Unstructured API services for processing by default. To process data locally instead, see the instructions at the end of this page.
For the Unstructured Ingest CLI and the Unstructured Ingest Python library, you can use the --partition-by-api
option (CLI) or partition_by_api
(Python) parameter to specify where files are processed:
-
To do local file processing, omit
--partition-by-api
(CLI) orpartition_by_api
(Python), or explicitly specifypartition_by_api=False
(Python).Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:
--api-key $UNSTRUCTURED_API_KEY
(CLI) orapi_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) orpartition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)- The environment variables
UNSTRUCTURED_API_KEY
andUNSTRUCTURED_API_URL
-
To send files to Unstructured API services for processing, specify
--partition-by-api
(CLI) orpartition_by_api=True
(Python).Unstructured API services also requires an Unstructured API key and API URL, by adding the following:
--api-key $UNSTRUCTURED_API_KEY
(CLI) orapi_key=os.getenv("UNSTRUCTURED_API_KEY")
(Python)--partition-endpoint $UNSTRUCTURED_API_URL
(CLI) orpartition_endpoint=os.getenv("UNSTRUCTURED_API_URL")
(Python)- The environment variables
UNSTRUCTURED_API_KEY
andUNSTRUCTURED_API_URL
, representing your API key and API URL, respectively.