Good day. I am working to setup tap-youtube-analytics, but the schema provide does not match our youtube report naming. For some reason they were changed in our account (still working on why), for example channel_basic is channel_basic_a2 instead. Is there a best practice for handling this?

You can override the schema via https://meltano.com/docs/plugins.html#extractors but this seems to be about the stream name.

@taylor @matthew_skinner Make sure to use the tap in the singer-io repo https://github.com/singer-io/tap-youtube-analytics . The bytecodeio repo, is just the first release. We are discussing limiting access to the bytecodeio repos, once they have been release to singer-io. As for the called functionality, I’m not sure. Check the singer-io tap, if the same functionality is still present, we can discuss next steps.

@charlie_killian I'll work on testing the Singer Repo. Thanks for the feedback. @taylor Can we point the meltano hub to the singer-repo as well? It's currently pointing at the bytecodeio repo here.

sure!

@tyler all repos should be pointed back Singer repos.

Good to know @charlie_killian - are there no taps where bytecode would be considered the primary maintainer?

I’m not sure, I’ll need to check with the team

@charlie_killian Do you know if the pypi distribution for tap-youtube-analytics is built on the singer repo or the bytecodeio repo? That's what I've been testing against.

MR to point to singer-io repos https://gitlab.com/meltano/hub/-/merge_requests/63/diffs