MySQL Databases and schemas VS containers and platform instances I have installed 0.8.26 to play with domains and containers and I have ingested metadata from a MySQL database. I can see that every schema has now its own container and that's all good. When I look at the parent of those containers (schemas), I see a container representing the database with a name of

none

. In Mysql, a database is pretty much the same as a schema, so it is unclear to me what the database should be... Seeing

none

is not what I was expecting. Is it to represent the fact that it is absent from Mysql? If so, would it be better to simply not create that container? Now if I want to document the hostname of the Mysql server in DataHub, is it when I need to use platform instances? I thought platform instances were used to differentiate different instances of Mysql servers, am I right? Looking for guidance here on how to use those concepts since I want to apply them to Datalakes in an Iceberg source I am currently working on.

Hello Eric, You make a good question. I’m going to try and talk to the core team members who worked on domains and let you know how this particular case for MySQL databases should work!

@modern-monitor-81461 platform instances are indeed what you use for differentiating different physical instances of MySQL servers

ok cool, thanks for the follow-up. Glad to see that I'm understanding this right

yeah, sorry, I was not aware of this