❓ I'm looking at the tranformers and documentation in metadata-ingestion. One use case I have for dbt ingestion is that I want to completely skip tests and seed data, until we can ensure that it's not just overwhelming noise in the UI. Is there a transformer (or can a custom one) to prevent MCEs from continuing on to ingestion?

how about using the file or console sink to inspect the generated output? Instead of piping it straight to datahub.

I'm not sure what my gain would be, by piping the output to console?

ah, my bad. i thought you just wanted to see what is produced by ingestion. misinterpreted your qn

no worries 😄 I think I've found an easier answer by going through the code base:

node_type_pattern.allow

I just need to check the manifest to ensure that

resource_type

does provide the info I need to target just table nodes

ah i thought the filter's didnt work for you i just tried transformer method, if you could identify which MCE is the one you don't want, you could return an empty set for ingest (which datahub will reject but allow the rest to go thru)