Panoply.io Destination Reference

Panoply is a fully managed data warehouse service that will spin up an Amazon Redshift instance in just a few clicks. With Panoply, you can use your favorite analysis, SQL, and visualization tools just like you would if you were creating a Redshift data warehouse on your own.

This guide serves as a reference for version 2 of Stitch’s Panoply destination.

Details and features

• Stitch features

• Destination details

• Pricing

Stitch features

High-level details about Stitch’s implementation of Panoply, such as supported connection methods, availability on Stitch plans, etc.

Destination details

Details about the destination, including object names, table and column limits, reserved keywords, etc.

Note: Exceeding the limits noted below will result in loading errors or rejected data.

Pricing

Pricing varies from plan to plan, but every Panoply plan includes:

• Unlimited queries
• Unlimited user accounts
• Automatic maintenance, vacuuming, and backups

Panoply charges based on the amount of data stored and offers several plan options for your needs. Refer to their pricing page for more information.

Replication

• Replication process overview

• Loading behavior

• Primary Keys

• Incompatible sources

Replication process overview

A Stitch replication job consists of three stages:

• Step 1: Data extraction

• Step 2: Preparation

• Step 3: Loading

Step 1: Data extraction

Stitch requests and extracts data from a data source. Refer to the System overview guide for a more detailed explanation of the Extraction phase.

Step 2: Preparation

During this phase, the extracted data is buffered in Stitch’s durable, highly available internal data pipeline and readied for loading. Refer to the System overview guide for a more detailed explanation of the Preparation phase.

Step 3: Loading

Stitch loads the data into Panoply.

Loading behavior

By default, Stitch will use Upsert loading when loading data into Panoply.

If the conditions for Upsert loading aren’t met, data will be loaded using Append-Only loading.

Refer to the Understanding loading behavior guide for more info and examples.

Primary Keys

Stitch requires Primary Keys to de-dupe incrementally replicated data. To ensure Primary Key data is available, Stitch creates a primary_keys table comment. The comment is an array of strings that contain the names of the Primary Key columns for the table.

For example: A table comment for a table with a single Primary Key:

'{"primary_keys":["id"]}'

And a table comment for a table with a composite Primary Key:

'{"primary_keys":["event_id","created_at"]}'

Note: Removing or incorrectly altering Primary Key table comments can lead to replication issues.

Incompatible sources

The Panoply destination has reported incompatibilities with some of Stitch's integrations. Refer to the table below for more info.

See all destination and integration incompatibilities.

Transformations

• System tables and columns

• Data typing

• JSON structures

• Column names

• Timezones

System tables and columns

Stitch will create the following tables in each integration’s dataset:

• _sdc_rejected

Additionally, Stitch will insert system columns (prepended with _sdc) into each table.

Data typing

Stitch converts data types only where needed to ensure the data is accepted by Panoply. In the table below are the data types Stitch supports for Panoply destinations, and the Stitch types they map to.

• Stitch type: The Stitch data type the source type was mapped to. During the Extraction and Preparing phases, Stitch identifies the data type in the source and then maps it to a common Stitch data type.
• Destination type: The destination-compatible data type the Stitch type maps to. This is the data type Stitch will use to store data in Panoply.
• Notes: Details about the data type and/or its allowed values in the destination, if available. If a range is available, values that exceed the noted range will be rejected by Panoply.

JSON structures

Panoply destinations don’t have native support for nested data structures. To ensure nested data can be loaded, Stitch will flatten objects and arrays into columns and subtables, respectively. For more info and examples, refer to the Handling nested data structures guide.

Column names

Column names in Panoply:

• Must contain only letters (a-z, A-Z), numbers (0-9), or underscores (_)
• Must begin with a letter

• Must be less than the maximum length of 115 characters. Columns that exceed this limit will be rejected by Panoply.

• Must not be prefixed or suffixed with any of Panoply’s or Stitch’s reserved keyword prefixes or suffixes

Stitch will perform the following transformations to ensure column names adhere to the rules imposed by Panoply:

Timezones

Panoply will store the value as TIMESTAMP WITHOUT TIMEZONE. In Panoply, this data is stored without timezone information and expressed as UTC.

Compare destinations

Not sure if Panoply is the data warehouse for you? Check out the Choosing a Stitch Destination guide to compare each of Stitch’s destination offerings.

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.