janis_puris
01/24/2023, 10:04 AMpublic
.
Works (public
schema)
meltano --environment=dev config meltano set database_uri '<postgresql://CHANGEME:CHANGEME@localhost:5432/meltano__dev>'
The systemdb tables are created in public
upon first etl
run
however this does not (systemdb
schema)
meltano --environment=dev config meltano set database_uri '<postgresql://sqlsvc__dpt__meltano_state:meltano@localhost:5432/meltano__dev?options=-csearch_path%3Dsystemdb>'
produces no errors.. but on first elt run, such as
meltano --environment=dev elt tap-CHANGEME target-CHANGEME --transform=skip --state-id=CHANGEME-to-CHANGEME
would produce following error
2023-01-24T09:57:35.507989Z [error ] (psycopg2.errors.InvalidSchemaName) no schema has been selected to create in
LINE 2: CREATE TABLE alembic_version (
^
[SQL:
CREATE TABLE alembic_version (
version_num VARCHAR(32) NOT NULL,
CONSTRAINT alembic_version_pkc PRIMARY KEY (version_num)
)
]
(Background on this error at: <https://sqlalche.me/e/14/f405>)
...
[MASSIVE STACK TRACE]
I'm following the official docs Targeting a PostgreSQL Schemajanis_puris
01/24/2023, 10:18 AMALTER USER CHANGEME SET search_path = 'systemdb';
and
MELTANO_DATABASE_URI='<postgresql://CHANGEME:CHANGEME@localhost:5432/meltano__dev>'
results in same error..
ProgrammingError: (psycopg2.errors.InvalidSchemaName) no schema has been selected to create in
Looks like might be something to do with sqlalchemy / psycopg2 and/or pg15 thinkspinMatt Menzenski
01/24/2023, 5:49 PMMELTANO_DATABASE_URI=<postgresql://user:pass@my.host:5432/meltano?options=-csearch_path%3Dmeltano>
to use a meltano
db and meltano
schemajanis_puris
01/24/2023, 5:50 PMjanis_puris
02/08/2023, 10:28 AM