The marketing team is looking to share data in an aggregate table with the sales organization, but the field names used by the teams do not match, and a number of marketing specific fields have not been approval for the sales org.
Which of the following solutions addresses the situation while emphasizing simplicity?
Creating a view is a straightforward solution that can address the need for field name standardization and selective field sharing between departments. A view allows for presenting a transformed version of the underlying data without duplicating it. In this scenario, the view would only include the approved fields for the sales team and rename any fields as per their naming conventions.
Databricks documentation on using SQL views in Delta Lake: https://docs.databricks.com/delta/quick-start.html#sql-views
Wenona
9 months agoJodi
9 months agoFrankie
9 months agoTonette
10 months agoHortencia
10 months agoDonte
10 months agoThad
10 months agoRobt
10 months agoNoel
11 months agoGaynell
11 months agoAudra
11 months agoDante
11 months agoAnnamae
11 months agoKina
11 months agoCassandra
11 months agoSina
11 months agoZona
2 years agoKristofer
2 years agoMee
2 years agoKenneth
2 years agoCarman
2 years agoBrinda
2 years agoGiuseppe
2 years agoWalton
2 years ago