Hello! I'm having a lot of issues when it comes to using

meltano run tap-mysql target-snowflake

Namely, every time a table at source has a column of type JSON, my loader will (correctly) create a table in Snowflake with column of type VARIANT. This makes sense, yet when I run the command I get a validation error to the tune of:

'[{"A": 10}, {"B": 12}]' is not of type null, object

Yet when I load this into a VARIANT as you typically can in Snowflake via

select parse_json('[{"A": 10}, {"B": 12}]');

Works just fine. ----- This type of error seems consistent across all the JSON columns I'm trying to load from my tap. Any ideas why this is happening or how I can fix it? As a workaround I tried adding a stream map to cast the value of those particular columns to string but that didn't seem to work (I'm probably misunderstanding how stream maps are supposed to be used) and in any case is not ideal for the long term, as ideally JSON types in MySQL should be shoved into Snowflake as a VARIANT as easily as

select parse_json(...)

Hi @Alexandre Pelletier! Which variant of tap-mysql is this?

Hey @Edgar Ramírez (Arch.dev)! This is using

extractors:
  - name: tap-mysql
    variant: transferwise
    pip_url: pipelinewise-tap-mysql
    metadata:
      '*':
        replication_method: LOG_BASED
loaders:
  - name: target-snowflake
    variant: meltanolabs
    pip_url: meltanolabs-target-snowflake
    config:
      load_method: overwrite
      validate_records: false

Thanks. I think the tap is serializing that to a string unfortunately: https://github.com/transferwise/pipelinewise-tap-mysql/blob/15a5be06273f85852d95b94f4e551aada61be05e/tap_mysql/sync_strategies/binlog.py#L232-L233 A fix was never merged 😕

Alright I'll try the other tap variants, thanks!