i stumbled upon this article titled "lakelouse tower of babel" while browsing tech forums (guess its time to change the title). basically says that when you try using multiple engines on shared data with open formats like apache iceberg, things can get messy real fast. each engine has its own way of handling sql identifiers and catalog names - like trying to speak 5 different languages in one room.
the article points out how important it is for everyone involved (yes, i mean all the db engineers) to use consistent naming conventions across engines so everything plays nice together like a well-oiled machine. kinda reminds me when we had shared projects back at uni where using someone else's file format always caused headaches because of different versions and settings.
so heres my $0.2:
are there any tools or plugins that help enforce these consistent naming conventions across engines? i mean, if youre working in a team with multiple db engineers pulling from the same data lakehouse - how do y'all ensure everyone is on thesame page without manual double-checks all day long?
anyone wanna chime and share their experiences or tools they use for this kind of cross-engine validation? lets break down these babel tower problems in a friendly, collaborative way.
found this here:
https://www.infoq.com/articles/lakehouse-sql-identifier-rules/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global