Using great expectations we should add tests for our source data so that we are notified if something changes. Also the documentation of the MaStR Source data set should be extended. The .yml files for the source description in dbt can then be transformed to OEMetadata schema.
When running docker-compose up, the dbt deps command is executet when the container docker_user_code is built. However after the building process, the volume for the dagter app data is mounted, overwriting the dbt package data created when running dbt deps initially.
When pandas 3.0 is introduced, there will be major changes to read_sql and to_sql. As these functions are used often in open-dapro we need to have this in mind.
Error log:
Database Error in model stg_charging_points (models/staging/charging_points/stg_charging_points.sql)
function replace(double precision, unknown, unknown) does not exist
LINE 33: ...T(REPLACE("Längengrad", ',', '.') AS float), CAST(REPLACE("B...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
compiled Code at target/run/energy_dbt/models/staging/charging_points/stg_charging_points.sql
mastr__temporal_expansion throws error
Database Error in model mastr__temporal_expansion (models/marts/marktstammdatenregister/mastr__temporal_expansion.sql)
column "power" does not exist
LINE 36: power,
Probably the docker setup can also be run by using docker compose command (which is installed together with docker). By that we can get rid of the additional installation of the standalone docker-compose command.
It would be great if someone could document oepn-dapro in our compendium. This will help to keep an overview of all our tools, and by providing a short description, users can better understand what this tool does in the context of the OE family.
If you don't want to go to the trouble of adding content to the compendium, it would be nice if you could provide the descriptive text in this issue so I can add it later.