Hi,
I’m looking for guidance on Naming standards to organize Schemas and underlying objects(tables, Materialized views) in a more efficient manner in Starburst Enterprise.
Our Materialized views are in hive and we use iceberg tables. The number of MVs in the structure layer, intermediate views are growing out of control. we have hundreds of views under many schemas. It is difficult to manage, search and know which views belong to consume, which ones are from harmonize(structure) layer…
Basically looking for best practices for layer, objects naming convention.
There are not really any standards around that. In many cases mimicking known naming conventions and hierarchies in your organization is appropriate and helps. Many organizations already have naming conventions around database names and such.
It will be important to figure out security controls and an owner for establishing a structure, documenting it, maintaining it, and enabling all users. All objects ideally also have metadata like descriptions, owners, and so on so that whoever finds the objects can make some sense of them. Users can then use command such as describe, show create .., and specific queries of the metadata to learn more.
With Starburst Enterprise you can also use data products to help with some of these aspects and encapsulate objects behind data products UI and facade.