Skip to main content

tap-snowflake

tap-snowflake is a Singer tap for Snowflake.

Built with the Meltano Tap SDK for Singer Taps.

Installation

pipx install git+https://github.com/MeltanoLabs/tap-snowflake.git

Configuration

Accepted Config Options

A full list of supported settings and capabilities for this tap is available by running:

tap-snowflake --about

tables configuration parameter.

An array of the table names that you want to sync. The table names should be fully qualified, including schema and table name.

NOTES:

  • This limits discovery to the tables specified for performance reasons. Do not specify tables if you intend to discover the entire available catalog.
  • Syntax to specify tables differs slightly from select (schema_name.table_name vs schema_name-table_name.*)

💡 When adding more elements to select ensure the table is specified in tables if using tables.

Example:

  ...
  tables:
    - schema_name1.table1
    - schema_name1.table2

Configure using environment variables

This Singer tap will automatically import any environment variables within the working directory's .env if the --config=ENV is provided, such that config values will be considered if a matching environment variable is set either in the terminal context or in the .env file.

Source Authentication and Authorization

This tap supports two authentication methods:

Key Pair Authentication

Key Pair authentication can be enabled by specifing either the private_key of the private_key_path, and optionally the private_key_passphrase if required.

Enabling Batch Messaging

This tap is built using the Meltano SDK and therefore supports a BATCH message type, in addition to the RECORD messages of the Singer spec. This can be enabled either by adding the following to your config.json:

{
  // ...
  "batch_config": {
    "encoding": {
      "format": "jsonl",
      "compression": "gzip"
    },
    "storage": {
      "root": "file://tests/core/resources",
      "prefix": "test-batch"
    }
  }
}

or its equivalent to your meltano.yml

config:
  plugins:
    extractors:
      - name: tap-snowflake
        config:
          batch_config:
            encoding:
              format: jsonl
              compression: gzip
            storage:
              root: "file://tests/core/resources"
              prefix: test-batch

Note: This variant of tap-snowflake does not yet support the INCREMENTAL replication strategy in BATCH mode. Follow here for updates.

arrow encoding

In addition to jsonl, encoding.format also accepts arrow:

{
  "batch_config": {
    "encoding": {
      "format": "arrow"
    },
    "storage": {
      "root": "file:///tmp/tap-snowflake-batches"
    },
    "batch_size": 500000
  }
}
Replication method With batch_config set
FULL_TABLE BATCH messages
INCREMENTAL BATCH messages

Unlike jsonl, which unloads rows to the Snowflake-managed internal user stage via COPY INTO and then downloads them (LIST/GET), arrow reads query results directly using snowflake-connector-python's native Arrow result format (Snowflake's wire format is already Arrow) -- no stage, intermediate JSON encoding, or extra download round trip. batch_size controls how many rows accumulate before a new Arrow IPC file is flushed (default 10000, matching the SDK's default). As with jsonl, batch files are written to local storage only and are not cleaned up by the tap -- the consumer owns their lifecycle.

Usage

You can easily run tap-snowflake by itself or in a pipeline using Meltano.

Executing the Tap Directly

tap-snowflake --version
tap-snowflake --help
tap-snowflake --config CONFIG --discover > ./catalog.json

Developer Resources

Initialize your Development Environment

curl -LsSf https://astral.sh/uv/install.sh | sh # https://docs.astral.sh/uv/getting-started/installation/
uv sync

Create and Run Tests

Create tests within the tap_snowflake/tests subfolder and then run:

uv run pytest

You can also test the tap-snowflake CLI interface directly using uv run:

uv run tap-snowflake --help

Testing with Meltano

Note: This tap will work in any Singer environment and does not require Meltano. Examples here are for convenience and to streamline end-to-end orchestration scenarios.

Your project comes with a custom meltano.yml project file already created. Open the meltano.yml and follow any "TODO" items listed in the file.

Next, install Meltano (if you haven't already) and any needed plugins:

# Install meltano
pipx install meltano
# Initialize meltano within this directory
cd tap-snowflake
meltano install

Now you can test and orchestrate using Meltano:

# Test invocation:
meltano invoke tap-snowflake --version
# OR run a test `elt` pipeline:
meltano elt tap-snowflake target-jsonl

SDK Dev Guide

See the dev guide for more instructions on how to use the SDK to develop your own taps and targets.

Metadata

Release files for meltanolabs-tap-snowflake 0.5.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for meltanolabs-tap-snowflake 0.5.5
File Size Uploaded
meltanolabs_tap_snowflake-0.5.5.tar.gz 17.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for meltanolabs-tap-snowflake 0.5.5
File Interpreter ABI Platform
meltanolabs_tap_snowflake-0.5.5-py3-none-any.whl Python 3 none any Details

Total release size: 37.1 kB

Release files / meltanolabs_tap_snowflake-0.5.5.tar.gz

Download URL meltanolabs_tap_snowflake-0.5.5.tar.gz
Size 17.9 kB
Tags Source
SHA-256 checksum
How to use checksums
02167dde8d13b71a9f0d68248d1e0d6995b141d4b470092ff962d3a21ed19294
BLAKE2b-256 checksum
How to use checksums
e53f09f6d28e1077077c24c116c5576cd57600cba089a29a8f03861d96d0e9db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release files / meltanolabs_tap_snowflake-0.5.5-py3-none-any.whl

Download URL meltanolabs_tap_snowflake-0.5.5-py3-none-any.whl
Size 19.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
26041018ebfae5697114414afe21595ce91fb58b650e6ed787aa38a51463ac3f
BLAKE2b-256 checksum
How to use checksums
4e0a3ee10d1302afcda4906b6789d17c79fbddb984d594fd5deb22541c2d9a6d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page