<@U06CQ9D5M5X> <@U06C8SN07SR> just published an ar...
# show-us-what-you-got
s
@aaron_phethean @daniel_walker just published an article on the Matatika plugin, the UI and Meltano! https://medium.com/@danielpdwalker/a-user-interface-for-meltano-397089465cd9
@aaron_phethean @daniel_walker had to pick it up now since I want to include it in the newsletter I'm drafting right now 😉
j
Is it possible to override the default port of the PostgreSQL container started as a part of Matatika lab? When evaluating locally, I always have a running PostgreSQL container serving as Meltano target, exposing 5432 port, so I can admin it e.g. from DBeaver.
a
Ah, that’s another case where a docker-compose.yml would be better. Using ‘meltano invoke matatika invoke’ is the SDK way to pass the command line args directly through. In our case to docker compose. I’ll see if I can get a docker command with port changed to work. Alternatively we could change the environment to connect to your Postgres. Let you know!
Hi @jan_soubusta - we discussed this today and have two thoughts: 1. we could help you run matatika-ce and have that run your standalone postgres 2. we could run the 'matatika' meltano utility postgres on a different default port - we think this might be worth doing anyway. @Reuben (Matatika) is going to reply here with a bit more detail on these ideas.
r
So, as Aaron mentioned, we talked about changing the port the
matatika
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)
j
To be honest, I am a little bit lost 😉 This week I have to focus on a meetup we organize and where I present. Next week we could schedule a short Zoom, where you could give me more context (and I can answer any question you might have), WDYT?
r
Yeah, sounds good. I'll speak to Aaron and we'll setup a meeting for sometime next week. 🙂 Any preference on date/time?
j
Monday, Wednesday, Friday, anytime after 2pm CET
r
Hi @jan_soubusta, we've just released
v0.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.

https://youtu.be/-9EsADCLJxgâ–¾

j
Will check it next week, this week is shorter (public holiday tomorrow and on Monday) and I am looking forward to rest 😉
a
Cool. Have a great holiday!