Hey everyone! I'm super new to Meltano, and trying to set up my first tap. I tried to run

tap-maestroqa

with

target-snowflake

, but keep getting a

CRITICAL 'bookmarks'

error.

meltano run tap-maestroqa target-snowflake

...
INFO MaestroQA: export completed
INFO Retrieved
INFO Syncing CSV file
CRITICAL 'bookmarks'

Does anyone have any idea what this means? Is this a Meltano error, or a tap specific error?

tap specefic

@timothy_ng I only see a reference to bookmarks in a few places in the tap for handling incremental state like this. I wonder if you run

meltano run tap-maestroqa target-snowflake --full-refresh

to exclude any previous state, if that will help

full refresh didn't do the trick, it's still throwing the

CRITICAL 'bookmarks'

error.

@timothy_ng I have one more hunch! In your meltano.yml file can you add this list of capabilities to your config? I think its not advertising the ability to track incremental state

pip_url: git+<https://github.com/Pathlight/tap-maestroqa.git>    
capabilities:
    - catalog
    - state
    - discover

this is what I currently have in my meltano.yml:

- name: tap-maestroqa
    variant: pathlight
    pip_url: git+<https://github.com/Pathlight/tap-maestroqa.git>
    config:
      api_token: **********************
      start_date: '2022-01-01T00:00:00Z'
    capabilities:
        - catalog
        - state
        - discover

I'm still running into the same error with a full refresh 🙁

Unfortunately I dont have access to maestroqa to test but I made one change in my fork that I suspect might be causing the issue. If you update your pip_url to

pip_url: git+<https://github.com/pnadolny13/tap-maestroqa.git>

and run

meltano install extractor tap-maestroqa --clean

to reinstall, I'd be curious if that works.

I changed my meltano.yml to:

- name: tap-maestroqa
    variant: pathlight
    # pip_url: git+<https://github.com/Pathlight/tap-maestroqa.git>
    pip_url: git+<https://github.com/pnadolny13/tap-maestroqa.git>
    config:
      api_token: uyxrqci2vwjfyll58girbni2uolrkhrjbwki83pv
      start_date: '2022-01-01T00:00:00Z'
    capabilities:
        - catalog
        - state
        - discover

then ran:

meltano install extractor tap-maestroqa --clean

then:

meltano run tap-maestroqa target-snowflake

and still no luck );

@timothy_ng I gave it one more shot at a couple changes to my fork that might fix it but again I dont have an account to test against. There should be no direct references to

bookmarks

anymore, I suspect that will fix it. If it fails again, would you try running it with invoke like

meltano invoke tap-maestroqa

. And posting the actual error message you see so its easier to debug

@pat_nadolny sorry for the late response, but it looks like it worked with no errors, thanks a bunch!

@timothy_ng Awesome!!! I created a PR to the main repo to get my changes added https://github.com/Pathlight/tap-maestroqa/pull/2. I'll post back once theyre merged so you can go back to using the default repo and I'll get rid of my fork

Great, thanks for your help Pat!

FYI the PR just got merged so you can use the default tap repo again!

Hey @pat_nadolny, I've just noticed that

tap-maestroqa

may not be grabbing every table available from the MaestroQA API. Is there anyone specific I can reach out to in order to add more tables to the tap?

@timothy_ng it looks like its retrieving section_scores and total_scores right now and the docs say theres also: _individual_answers, annotations, and csat._ That are documented https://intercom.help/maestroqa/en/articles/1363737-exporting-raw-scores. It looks like all it would take is to create json schema files similar to section_scores.json for the new streams you want to add. Id recommend creating an issue in the repo to log this and then if you're up for it you can create a PR with those json schemas. Does that make sense?

Perfect, got it. Thanks!

Awesome! Let me know if you get hung up on anything and I'd be happy to help

Listed the issue in the repo 🙋🏻‍♂️

@timothy_ng it looks like one of the links you put in the issue is to a looker instance, was that supposed to be a docs link?

ahhh, nice catch! fixed.