@pat_nadolny looks like we’re getting some reports that https://hub.meltano.com/extractors/tap-parquet is starting to not work for folks. We should reassess the gold badge on it.

Yeah that one doesnt look like its in the best shape, its on SDK version 0.1.0.

I think that would make sense!

I think that would make sense!

Was that related to responsiveness or forking the repo? 😅

sorry - responsiveness. Derek’s working on tap-universal-file and I’d rather we invest in that than fork it.

What happens if I have a tap that I haven't updated in a while because it's stable and the target API hasn't changed? Should that negatively impact the tap responsiveness score?

yeah, fair point. It’s not an ideal solution but the lack of any activity makes folks question it. I wonder if there’s utility in having a part of the README that’s regularly updated with testing data? We could do badges to show that tests are passing and/or data is flowing. I know you all are testing many of your connectors daily and we should surface that info somehow

Yeah, that's fair. I wondered if you guys had telemetry on runs to identify plugins used and success of each block (although I think you might need some more granular info, for example, to discern between the tap/target processes of a single EL block)? Of course, another challenge there would be to (ideally) filter out development testing (i.e. the plugin does not exist on the hub or has a

maintenance_status

of anything but

active

) and user errors (e.g. bad config) from legitimate failures.

Right - we do have some of that data (and indeed we see 23 projects with tap-parquet but only ~100 executions over 3 months) and we don’t currently analyze the exit codes. We have that data but we just haven’t updated the Hub around it.

Nice, good to know. Sorry to hijack your thread! 😅