We expect the output of cat out_fail.txt | poetry run meltano-map-transform --config config.txt > out_mapped to have a 3rd stream of question_prod_1_test created. It isn't created.
Output (out_mapped) is the same as out_fail.txt
Now if you move the SCHEMA message for the User-* stream to the beginning of the file everything works as expected. out_success.txt is an example of this.
(Converted to .txt so it would upload to github, 🙄 )
out_fail.txt
out_success.txt
config.txt
{
"stream_maps": {
"question_prod_1_test": {
"__source__": "User-pzjs3twtm2y4ip6uvfvy6ukhpa-prod"
}
}
}
config.txt
re: https://meltano.slack.com/archives/C01TCRBBJD7/p1671688563297449
Very hard to debug this for end meltano users, I think meltano/meltano#3232 would make life a lot easier for folks as you could play around with your mappers
We expect the output of
cat out_fail.txt | poetry run meltano-map-transform --config config.txt > out_mappedto have a 3rd stream ofquestion_prod_1_testcreated. It isn't created.Output (out_mapped) is the same as
out_fail.txtNow if you move the
SCHEMAmessage for theUser-*stream to the beginning of the file everything works as expected.out_success.txtis an example of this.(Converted to .txt so it would upload to github, 🙄 )
out_fail.txt
out_success.txt
config.txt
config.txt
re: https://meltano.slack.com/archives/C01TCRBBJD7/p1671688563297449
Very hard to debug this for end meltano users, I think meltano/meltano#3232 would make life a lot easier for folks as you could play around with your mappers