Hi community, we prefer postgres to mysql (aligns better with our stack) so I'd like to use postgres as backend for gms. However, the helm chart contains a lot of mysql-specific variables, and no mention of postgres. Does the helm chart support postgres? https://github.com/acryldata/datahub-helm/tree/master/charts/datahub

Hi. Unfortunately, postgres-setup is not there. We are planning on adding it soon. If you can run this sql file https://github.com/linkedin/datahub/blob/master/docker/mysql-setup/init.sql using the postgres client you are good to go. Other than that you need to set the following under global.sql in the values.yaml file.

host: "<<host>>:<<port>>"
url: "jdbc:postgresql://<<host>>:<<port>>/datahub"
driver: "org.postgresql.Driver"

To switch gms to talk to postgres! All other configs are the same.

Hello, I’m also interested in learning about Postgres setup. Not helm deployment specific question, but while browsing the docker folder, I noticed that mysql and mysql-setup init.sql script creates “metadata_aspect_v2” and “metadata_index” tables, and postgres and mariadb init.sql script only creates “metadata_aspect_v2”. Was “metadata_index” table intentionally left out for postgres and mariadb or should it be created for those db as well?

That table is not uses as of now. It was used at LinkedIn to provide a strongly consistent secondary index. However, we currently do not support this

Thank you for the clarification! I will use the postgres init.sql as reference.

You will have to copy over the database creation logic. also make sure the table doesn’t exist before creating a new one

Thanks for getting back to me! I'll file an issue on this for now, and use MySql temporarily. Also thanks for a great product 💪

@gifted-queen-61023 ☝️ 😬