The Snowflake sink connector pulls data from Pulsar topics and persists data to Snowflake.

Features

This section describes the features of the Snowflake sink connector. For details about how to configure these features, see how to configure.

Delivery guarantees

The Pulsar IO connector framework provides three delivery guarantees: at-most-once, at-least-once, and effectively-once.

Currently, the Snowflake sink connector only supports the at-least-once delivery guarantee semantic.

Table name mapping

The Snowflake sink connector supports automatically creating a table when the table does not exist. You can configure the following options:

autoCreateTable=true

The Snowflake sink connector allows you to specify the mapping relationship between topics and tables. Each topic and its mapped table name should be separated by a colon. The parameter topic2table see example below:

topic2table=topic1:table1,topic2:table2

Metadata Fields

There are two fields in the table: metadata and content. Metadata is ancillary information in content, such as topic, messageId, publishTime, and so on. By default, the following metadata fields of Pulsar will be created as the metadata:

metadataField=__message_id__,__partition__,__topic__,__event_time__

Data format types

The snowflake connector supports converting some Pulsar schemas, as listed in the following table.

Batch progress

To increase write throughput, you can configure the buffer size and latency for the Snowflake sink connector.

bufferCountRecords = 10_000
bufferSizeBytes = 5_000_000
bufferFlushTimeInSeconds = 120

How to get

This section describes how to get the Snowflake sink connector.

Work with Function Worker

You can get the Snowflake sink connector using one of the following methods if you use Pulsar Function Worker to run the connector in a cluster.

• Download the NAR package from the download page .

• Build it from the source code.

To build the Snowflake sink connector from the source code, follow these steps.

1. Clone the source code to your machine.

   git clone https://github.com/streamnative/pulsar-io-snowflake
   

2. Build the connector in the pulsar-io-snowflake directory.

   mvn clean install -DskipTests
   

   After the connector is successfully built, a NAR package is generated under the target directory.

   ls target
   pulsar-io-snowflake-2.10.5.17.nar
   

Work with Function Mesh

You can pull the Snowflake sink connector Docker image from the Docker Hub if you use Function Mesh to run the connector.

How to configure

Before using the Snowflake sink connector, you need to configure it. This table outlines the properties and the descriptions.

Work with Function Worker

You can create a configuration file (JSON or YAML) to set the properties if you use Pulsar Function Worker to run connectors in a cluster.

Example

• JSON

   {
       "tenant": "public",
       "namespace": "default",
       "name": "snowflake-sink",
       "archive": "connectors/pulsar-io-snowflake-2.10.5.17.nar",
       "inputs": [
         "test-snowflake-pulsar"
       ],
       "parallelism": 1,
       "retainOrdering": true,
       "processingGuarantees": "ATLEAST_ONCE",
       "sourceSubscriptionName": "sf_sink_sub",
       "configs": {
         "user": "TEST",
         "host": "ry77682.us-central1.gcp.snowflakecomputing.com:443",
         "schema": "DEMO",
         "warehouse": "SNDEV",
         "database": "TESTDB",
         "privateKey": "SECRETS"
     }
   }
  

• YAML

  tenant: public
  namespace: default
  name: snowflake-sink
  parallelism: 1
  inputs:
    - test-snowflake-pulsar
  archive: connectors/pulsar-io-snowflake-2.10.5.17.nar
  sourceSubscriptionName: sf_sink_sub
  retainOrdering: true
  processingGuarantees: ATLEAST_ONCE
  configs:
    user: TEST
    host: ry77682.us-central1.gcp.snowflakecomputing.com:443
    schema: DEMO
    warehouse: SNDEV
    database: TESTDB
    privateKey: SECRETS
  

Work with Function Mesh

You can create a CustomResourceDefinitions (CRD) to create a Snowflake sink connector. Using CRD makes Function Mesh naturally integrate with the Kubernetes ecosystem. For more information about Pulsar sink CRD configurations, see sink CRD configurations.

You can define a CRD file (YAML) to set the properties as below.

apiVersion: compute.functionmesh.io/v1alpha1
kind: Sink
metadata:
  name: snowflake-sink-sample
spec:
  image: streamnative/pulsar-io-snowflake:2.10.5.17
  replicas: 1
  maxReplicas: 1
  retainOrdering: true
  input:
    topics: 
      - persistent://public/default/test-snowflake-pulsar
  sinkConfig:
    user: TEST
    host: ry77682.us-central1.gcp.snowflakecomputing.com:443
    schema: DEMO
    warehouse: SNDEV
    database: TESTDB
    privateKey: SECRETS
  pulsar:
    pulsarConfig: "test-pulsar-sink-config"
  resources:
    limits:
      cpu: "0.2"
      memory: 1.1G
    requests:
      cpu: "0.1"
      memory: 1G
  java:
    jar: connectors/pulsar-io-snowflake-2.10.5.17.nar
  clusterName: test-pulsar
  autoAck: false

How to use

You can use the Snowflake sink connector with Function Worker or Function Mesh.

Work with Function Worker

You can use the Snowflake sink connector as a standalone connector or a built-in connector as below.

Use it as standalone connector

If you already have a Pulsar cluster, you can use the Snowflake sink connector as a standalone connector directly.

This example shows how to create a Snowflake sink connector on a Pulsar cluster using the pulsar-admin sinks create command.

PULSAR_HOME/bin/pulsar-admin sinks create \
--sink-config-file <snowflake-sink-config.yaml >

Use it as built-in connector

You can make the Snowflake sink connector as a built-in one and use it on a standalone cluster.

This example describes how to use the Snowflake sink connector to fetch data from Pulsar topics and save data to Snowflake tables in standalone mode.

Prerequisites

• Install Pulsar locally. For details, see set up a standalone Pulsar locally.

Steps

1. Copy the NAR package to the Pulsar connectors directory.

   cp pulsar-io-snowflake-2.10.5.17.nar PULSAR_HOME/connectors/pulsar-io-snowflake-2.10.5.17.nar
   

2. Start a Pulsar cluster in standalone mode.

   PULSAR_HOME/bin/pulsar standalone
   

3. Run the Snowflake sink connector locally.

   PULSAR_HOME/bin/pulsar-admin sinks localrun \
   --sink-config-file <snowflake-sink-config.yaml>
   

   Or, you can create a connector for the Pulsar cluster.

   PULSAR_HOME/bin/pulsar-admin sinks create \
   --sink-config-file <snowflake-sink-config.yaml>
   

4. Send messages to a Pulsar topic.

   This example sends ten “hello” messages to the test-snowflake-pulsar topic in the default namespace of the public tenant.

   PULSAR_HOME/bin/pulsar-client produce public/default/test-snowflake-pulsar --messages hello -n 10
   

5. Query the data from the Snowflake table. For details, see Snowflake Quick Tour.

Work with Function Mesh

This example describes how to create a Snowflake sink connector for a Kubernetes cluster using Function Mesh.

Prerequisites

• Create and connect to a Kubernetes cluster.

• Create a Pulsar cluster in the Kubernetes cluster.

• Install the Function Mesh Operator and CRD into the Kubernetes cluster.

• Prepare Snowflake service. For details, see Getting Started with Snowflake.

Step

1. Define the Snowflake sink connector with a YAML file and save it as sink-sample.yaml.

   This example shows how to publish the Snowflake sink connector to Function Mesh with a Docker image.

    apiVersion: compute.functionmesh.io/v1alpha1
    kind: Sink
    metadata:
      name: snowflake-sink-sample
    spec:
      image: streamnative/pulsar-io-snowflake:2.10.5.17
      className: org.apache.pulsar.ecosystem.io.snowflake.SnowflakeSinkConnector
      replicas: 1
      maxReplicas: 1
      retainOrdering: true
      input:
        topics: 
          - persistent://public/default/test-snowflake-pulsar
      sinkConfig:
         user: TEST
         host: ry77682.us-central1.gcp.snowflakecomputing.com:443
         schema: DEMO
         warehouse: SNDEV
         database: TESTDB
         privateKey: SECRETS
      pulsar:
        pulsarConfig: "test-pulsar-sink-config"
      resources:
        limits:
         cpu: "0.2"
         memory: 1.1G
        requests:
         cpu: "0.1"
         memory: 1G
      java:
        jar: connectors/pulsar-io-snowflake-2.10.5.17.nar
      clusterName: test-pulsar
      autoAck: false
   

2. Apply the YAML file to create the Snowflake sink connector.

   Input

   kubectl apply -f <path-to-sink-sample.yaml>
   

   Output

   sink.compute.functionmesh.io/snowflake-sink-sample created
   

3. Check whether the Snowflake sink connector is created successfully.

   Input

   kubectl get all
   

   Output

   NAME                                         READY   STATUS      RESTARTS   AGE
   pod/snowflake-sink-sample-0                   1/1    Running     0          77s
   

   After that, you can produce and consume messages using the Snowflake sink connector between Pulsar and Snowflake.