Performance on Storage Zone "__current" views - Cloudera
We are using Replicate to replicate data from the source database to the Landing zone database on Cloudera. We are using a Compose Hive project to move the data from the Landing zone to the tables in the Storage zone.
- ACID Transactions: Create tables without ACID transactions - Project Type: Historical Data Store - When a record is deleted from the landing database: Do nothing
Currently all tables/views are created by Compose using default settings.
Our BI developers would like to know how the performance on the "__current" views on big tables can be improved. Are there any best practices available that could guide us, or should this be done in the view definition generated by Compose?