Why does the Redshift destination require a user with create on database permissions? Is there anyway around this?

It needs because of normalization step

and theres no way around that?

@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2593 to ensure timely resolution!

Where is the normalization happening? From the docs:

Each stream will be output into its own raw table in Redshift. Each table will contain 3 columns:

• `_airbyte_ab_id`: a uuid assigned by Airbyte to each event that is processed. The column type in Redshift is

VARCHAR

.

• `_airbyte_emitted_at`: a timestamp representing when the event was pulled from the data source. The column type in Redshift is

TIMESTAMP WITH TIME ZONE

.

• `_airbyte_data`: a json blob representing with the event data. The column type in Redshift is

VARCHAR

but can be be parsed with JSON functions.

I don’t think so, it will try to validate the permission during the check connection stage trying to create a schema/table.