or_barda
10/01/2020, 1:23 PMjulian_knight
10/01/2020, 5:49 PMmeltano select to see what streams will get selected, and running either that command or meltano invoke (could be any invoke call to the tap, even --help) will generate a catalog file in .meltano/run/[tap-name] that you can inspect. Is that what you're asking?julian_knight
10/01/2020, 6:16 PMmeltano select --listjulian_knight
10/01/2020, 11:36 PM--dump is new functionality I had missed. Try adding --dry to the command so it doesn't actually run the pipeline @or_bardadouwe_maan
10/05/2020, 4:00 PMmeltano elt --dump=<file> already doesn't actually run the pipeline!
I tried to make this clear in the docs (https://meltano.com/docs/command-line-interface.html#elt, emphasis mine):
Aoption can be passed (along with any of the other options) to dump the content of a pipeline-specific generated file to STDOUT instead of actually running the pipeline. This can aid in debugging extractor catalog generation, pipeline state lookup, and pipeline-specific configuration.--dump
douwe_maan
10/05/2020, 4:01 PM--dump is an option on meltano elt and not a command of its own is that the entire ELT context (extractor, loader, optional transformer, job ID) is needed to correctly generate the files, which are then dumped to STDOUT instead of passed on to the plugin.or_barda
10/06/2020, 8:54 AM