-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New Adapter Information Sheet
The following questions are intended to provide information about a warehouse, for use in building a new dbt adapter. Different data warehouses have pretty different semantics, so some of these questions may be more applicable than others. Where possible, please provide as much detail as you can!
Please copy this questionnaire to a GitHub gist, then fill out answers to the questions to the best of your ability. Where you're done, please post a link to the public gist in the relevant issue. If the issue does not already exist, please create it first.
-
What options are there for connecting to the warehouse? Eg: ODBC, a python module, etc
-
Is there a consensus around which of the options in #1 is the most featureful/best supported/most mature/etc option?
-
Does the warehouse support namespaces/schemas/datasets (or similar)?
-
Can schemas/namespaces be created using SQL? Eg:
create schema my_schema
-
Does the warehouse support logical databases?
-
Does the warehouse support standard-ish SQL? Are there any noteworthy caveats?
-
Are transactions supported?
-
Can tables be created with
create table schema.table as (...)
? -
Can views be created with
create view schema.view as (...)
? -
Can tables/views be renamed with
alter table {table_name} rename to {new_name}
? -
Does the warehouse support insert statements? Any caveats?
-
Does the warehouse support delete statements? Any caveats?
-
Does the warehouse support update statements? Any caveats?
-
Does the warehouse support merge statements? Any caveats?
-
Does the warehouse support drop table/drop view statements? Any caveats?
-
Does the warehouse support
truncate
statements? Any caveats? -
Does the warehouse support temporary tables? Any caveats?
-
Can queries be cancelled?
-
Are views bound to the relations they select from? Ie. do
drop table
statements require a...cascade
argument? -
Does the warehouse support querying for existing relations (ie. their existence and type)? Is this via an API call or a SELECT statement? Eg:
select * from information_schema.tables
. -
Does the warehouse support querying for the the columns in a relation? Is this via an API call or a SELECT statement? Eg:
select * from information_schema.columns
-
Can columns be added and removed using DDL? Eg:
alter table add column <name> <type>
? -
Does the warehouse support non-standard performance configurations? Ie. clustering, partitioning, sort/dist keys, etc. What are they, and how are they used? Can they be supplied in
create table as
statements? -
Which column types does the warehouse support? Are text types varchars (with sizes) or unsized
string
columns? Are numeric types (with fixed precision) supported? Is there a different type for timestamps with timezones? Any caveats? -
Does the warehouse support column-level constraints (eg. unique, not null, foreign key, primary key)? Are they enforced? Can they be defined in
create table as
statements? -
Are there other noteworthy quirks/features of the warehouse that have not been specified above? If so: please enumerate them here!