I think it’s to normalize case – it’s putting the canonical value back in.
On 10/25/17, 11:03 AM, "Alan Gates" <[email protected]> wrote: Looking at this code in the TransactionalValidationListener, around line 186: *if *(hive_metastoreConstants.*TABLE_IS_TRANSACTIONAL*.equalsIgnoreCase(key)) { transactional = parameters.get(key); parameters.remove(key); } Why does it remove the parameter after checking? In local metastore cases where the thrift object could actually be shared between client and server, I think this could lead to a problem if someone does a create table followed by an alter table using the same thrift object. Alan.
