> reuse the transactional_properties and add 'read_only' as a new value. With > read-only tables, all INSERT, UPDATE, DELETE statements will fail at Hive > front-end.
This is actually a common ask when it comes to OnPrem -> Cloud REPL streams, to avoid diverging. The replicated data having its own updates is very problematic for CDC style ACID replication into the cloud. Ranger authorization works great for this, though it is all-or-nothing right now. At some point in the future, I wish I could lock up specific fields from being updated in ACID. Cheers, Gopal
