Hi all I am using a postgres store atm via a jdbc connector to create my type = Paimon catalog, as per below, this is for my outbound data flow.
CREATE CATALOG c_paimon WITH ( 'type' = 'paimon' ,'metastore' = 'jdbc' ,'catalog-key' = 'jdbc' -- PostgreSQL JDBC connection ,'uri' = 'jdbc:postgresql://postgrescat:5432/flink_catalog?currentSchema=paimon' ,'jdbc.user' = 'dbadmin' ,'jdbc.password' = 'dbpassword' ,'jdbc.driver' = 'org.postgresql.Driver' -- MinIO S3 configuration with SSL/TLS (if needed) ,'warehouse' = 's3://warehouse/paimon' -- bucket / datastore ,'s3.endpoint' = 'http://minio:9000' -- MinIO endpoint ,'s3.access-key' = 'mnadmin' ,'s3.secret-key' = 'mnpassword' ,'s3.path-style-access' = 'true' -- Required for MinIO -- Default table properties ,'table-default.file.format' = 'parquet' ); CREATE DATABASE IF NOT EXISTS c_paimon.outbound; I create a couple of tables in c_paimon.outbound. ... => - adults, - children, - families etc. - addresses - potentially - accounts - potentially For the inbound stream i'm a bit stuck atm. - adults, - children - families For now I'm using the below, but I'd like to make it persistent, even better would/could be a second schema in my postgres database. CREATE CATALOG postgres_catalog WITH ('type'='generic_in_memory'); CREATE DATABASE IF NOT EXISTS postgres_catalog.inbound; I'd like to avoid HMS... trying specifically not to use it, to create a simpler stack Suggestions/examples pls. G -- You have the obligation to inform one honestly of the risk, and as a person you are committed to educate yourself to the total risk in any activity! Once informed & totally aware of the risk, every fool has the right to kill or injure themselves as they see fit!
