Sven Balnojan
03/28/2023, 10:57 AMSven Balnojan
03/28/2023, 10:57 AMjan_soubusta
03/28/2023, 3:07 PMaaron_phethean
03/28/2023, 4:30 PMaaron_phethean
03/29/2023, 9:05 AMReuben (Matatika)
03/29/2023, 10:04 AMmatatika utility db service runs on by default, which would fix this issue for you as-is (again, most likely we will end up doing this anyway).
Part of the reason we run a db service in the first place is so that pipeline runs have somewhere to load data into by default, which makes the onboarding process for a user really simple (no external services and less initial configuration required). In your case, db functions the in same way as the PostgreSQL container you are running, so it should be possible use it as a direct substitute. In this way, you would not have to supply any configuration for where to load data into in the UI, since we can load directly to db through our Warehouse store connection - have a look at the PR we made to your `data-pipeline` project for more context.
You could also run matatika-ce and directly control the configuration of db to your liking in the root docker-compose.yml - this is also possible with the matatika utility but is currently hidden away within .meltano (outside of source control) due to implementation.
Let us know if you have any thoughts. 😄
(cc @gabriel_ciobotaru)jan_soubusta
03/29/2023, 10:50 AMReuben (Matatika)
03/29/2023, 10:54 AMjan_soubusta
03/29/2023, 11:08 AMReuben (Matatika)
04/05/2023, 2:54 PMv0.4.0 of the matatika extension, which adds support for configuring the database port used by the service (see meltano invoke matatika lab --help). It's not quite on Meltano Hub yet (pending this PR), but I've already added it to our gooddata-data-pipeline PR. You can also try out the exact demo we showed you on Monday from this branch, complete with dbt project changes and all.
jan_soubusta
04/06/2023, 6:40 AMaaron_phethean
04/06/2023, 7:50 AM