Hey @anton
Really appreciate the help.
We’re getting closer and closer as time goes on. I updated the transformer to 0.8.0 and am using AMI 6.0 and it gets past the transformer step but fails at the loader step for an error that makes no sense
2020-11-02T21:28:14.041Z: Launching Snowflake Loader. Fetching state from DynamoDB
2020-11-02T21:28:14.918Z: State fetched, acquiring DB connection
2020-11-02T21:28:16.309Z: DB connection acquired. Loading...
2020-11-02T21:28:16.972Z: Existing column [event_id VARCHAR(36) NOT NULL] doesn't match expected definition [event_id CHAR(36) NOT NULL UNIQUE] at position 7
2020-11-02T21:28:16.972Z: Existing column [domain_sessionidx INTEGER] doesn't match expected definition [domain_sessionidx SMALLINT] at position 17
2020-11-02T21:28:16.972Z: Existing column [geo_country VARCHAR(2)] doesn't match expected definition [geo_country CHAR(2)] at position 19
2020-11-02T21:28:16.972Z: Existing column [geo_region VARCHAR(3)] doesn't match expected definition [geo_region CHAR(3)] at position 20
2020-11-02T21:28:16.972Z: Existing column [tr_currency VARCHAR(3)] doesn't match expected definition [tr_currency CHAR(3)] at position 107
2020-11-02T21:28:16.972Z: Existing column [ti_currency VARCHAR(3)] doesn't match expected definition [ti_currency CHAR(3)] at position 111
2020-11-02T21:28:16.972Z: Existing column [base_currency VARCHAR(3)] doesn't match expected definition [base_currency CHAR(3)] at position 113
2020-11-02T21:28:16.972Z: Existing column [domain_sessionid VARCHAR(128)] doesn't match expected definition [domain_sessionid CHAR(128)] at position 121
I tried manually modifying the column type to be char instead of varchar but to snowflake it seems to be the same thing. Any idea of what it could be?