heya - just scoping out meltano for the first time...
# troubleshooting
b
heya - just scoping out meltano for the first time. trying to use mysql tap but getting error
Exception: only INCREMENTAL, LOG_BASED, and FULL TABLE replication methods are supported
. meltano.yaml:
Copy code
extractors:
  - name: tap-mysql
    variant: transferwise
    pip_url: pipelinewise-tap-mysql
    config:
      database: bens_db
    select:
    - '*.*'
    metadata:
      bens_table:
        replication-method: INCREMENTAL
        replication-key: date_modified
the metadata doesnt seem to have been added to
.meltano/run/tap-mysql/tap.properties.json
(but the table and its columns have been) can anyone give me a hint what i might be doing wrong?
v
Output the catalog to take a look, is the easiest debug step. With meltano elt https://meltano.com/docs/command-line-interface.html#how-to-use-4
--dump=catalog > catalog
Invoke you can do the same. My guess is that you are selecting a bunch more streams then just bens_table. You could change your select to 'bens_table.*' and that might just work right away too
b
hey derek - dump=catalog shows the correct table/columns (no more no less), but the metadata
Copy code
replication-method: INCREMENTAL
replication-key: date_modified
are nowhere to be see
Copy code
select:
- 'bens_table.*'
shows no difference 馃槙
v
Is the stream name correct? Maybe bens_table isn't matching? I'm not sure if running elt in debug mode would tell you if the streams being matched or not, it might help
maybe bens_table isn't matching so it's not adding the INCREMENTAL metadata info
Could try
Copy code
metadata:
      '*':
        replication-method: INCREMENTAL
To see if that's the case. There may be a better way to tell if it's matching or not
b
Copy code
select:
- '*.*'
metadata:
  bens_db-bens_table:
    replication-method: INCREMENTAL
    replication-key: date_modified
this works
"tap_stream_id": "bens_db-bens_table"
weird, but ok!
thanks for your help!
v
No problemo! Glad I could help
And yeah the tap that you use makes up the stream name based on the data it sees. So for tap-mssql it decided to do the $dbname-$tablename for the stream names. Each tap handles these slightly different depending on the data. How I like to handle it is to run the tap in discovery mode, and then output the catalog to see what the data looks like first, then I build out my select / metadata
A lot of the singer / meltano stuff is getting the right mental model in your head. Someday it'd probably be good to have video tutorials or something to explain thought processes and things
b
tbh, filling in (and not truncating) the help descs for the cli would be a good step forward!
a
@ben_marengo - I can see how that could be confusing. I鈥檝e logged an issue in our issue tracker to improve this: Add `--help `docs for meltano CLI (#2716) 路 Issues 路 meltano / Meltano 路 GitLab Thanks for the feedback on this.