But if I use a recipe to publish a Postgres schema, the recipe uses urnlidataPlatform:postgresql and I do not get a nice Postgres icon in the GUI

c.l.m.k.MetadataAuditEventsProcessor - {com.linkedin.metadata.snapshot.DatasetSnapshot={urn=urn:li:dataset:(urn:li:dataPlatform:postgresql,myapp.public.source_table_c,PROD), aspects=[{com.linkedin.schema.SchemaMetadata={created={actor=urn:li:corpuser:etl, time=1619631529974}, platformSchema={com.linkedin.schema.MySqlDDL={tableSchema=}}, lastModified={actor=urn:li:corpuser:etl, time=1619631529974}, schemaName=myapp.public.source_table_c, fields=[{fieldPath=id, nullable=true, type={type={com.linkedin.schema.NumberType={}}}, nativeDataType=INTEGER(), recursive=false}, {fieldPath=col1, nullable=true, type={type={com.linkedin.schema.StringType={}}}, nativeDataType=VARCHAR(length=255), recursive=false}], version=0, platform=urn:li:dataPlatform:postgresql, hash=}}

Thanks for flagging this @steep-pizza-15641! Looks like we're following the sqlalchemy approach of

postgresql

for the scheme string, but on the datahub backend, the platform metadata is only registered for

postgres

. Will fix it! (either standardize on

postgres

or

postgresql

)

yep I’m on it

Amazing turnaround time thank!

It’s still pretty ad-hoc - let me cut one right now

confirmed fixed thanks