SourceTable objects, then convert those source tables into Kumo Table objects for your graph.
Connector classes
| Connector | Use for | Required setup |
|---|---|---|
S3Connector | CSV or Parquet files in Amazon S3 | Kumo deployment role can read the bucket/prefix |
GCSConnector | CSV or Parquet files in Google Cloud Storage | Kumo workload identity can read the bucket/prefix |
ADLSConnector | CSV or Parquet files in Azure Data Lake Storage | Kumo workload identity can read abfs:// or abfss:// paths |
SnowflakeConnector | Tables and views in a Snowflake schema | Snowflake account, warehouse, database, schema, and credentials unless using native SPCS auth |
DatabricksConnector | Tables in a Databricks catalog | Databricks host plus warehouse/cluster/catalog and OAuth or PAT credentials |
BigQueryConnector | Tables in a BigQuery dataset | Project, dataset, and service-account credentials |
GlueConnector | Partitioned Parquet tables in AWS Glue Catalog | Glue catalog metadata and IAM access to the backing S3 data |
FileUploadConnector | Local or remote CSV/Parquet files uploaded into Kumo | Use upload() before reading the table |
GroupConnector | Admin-managed connectors in RBAC-enabled workspaces | Select a group, then call kumo.list_group_connectors() |
If you use Kumo in Snowpark Container Services,
SnowflakeConnector is the supported connector type.Object storage connectors
Object storage connectors share the same access pattern. Create the connector with a root directory and read tables by relative table name. If you omitroot_dir, pass the full table path to table().
Warehouse connectors
Warehouse connectors create or attach to named Kumo connector resources. You can supply credentials directly or set the documented environment variables before constructing the connector.Snowflake
SnowflakeConnector can also use SNOWFLAKE_USER, SNOWFLAKE_PASSWORD, SNOWFLAKE_PRIVATE_KEY, and SNOWFLAKE_PRIVATE_KEY_PASSPHRASE environment variables. In SPCS environments initialized with snowflake_credentials, those credentials are reused when connector credentials are omitted; when initialized from a Snowflake notebook with snowflake_application, the SDK can create a native Snowflake connector without explicit connector credentials.
Databricks
token or DATABRICKS_TOKEN) or OAuth client credentials (client_id/client_secret or DATABRICKS_CLIENT_ID/DATABRICKS_CLIENT_SECRET), not both.
BigQuery
BIGQUERY_PRIVATE_KEY_ID, BIGQUERY_PRIVATE_KEY, BIGQUERY_CLIENT_ID, BIGQUERY_CLIENT_EMAIL, BIGQUERY_TOKEN_URI, and BIGQUERY_AUTH_URI.
AWS Glue
GlueConnector currently targets partitioned Parquet tables registered in the Glue Catalog.
Reusing existing connectors
For connectors that are stored in Kumo, retrieve a connector created earlier or created in the UI withget_by_name().
Uploaded files
UseFileUploadConnector when you have a local file or a remote file/directory that should be uploaded into Kumo-managed storage before it is used as a source table.
Group connectors
In RBAC-enabled workspaces, administrators can expose shared connectors at the group level. Users list and select those connectors instead of creating connectors with raw credentials.group and project before listing group connectors.
After selecting source tables
After a connector returnsSourceTable objects, continue with table and graph construction: