[ https://issues.apache.org/jira/browse/HIVE-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116154#comment-15116154 ]
Sergey Shelukhin commented on HIVE-12916: ----------------------------------------- Actually, why do we even want to do it on master? It breaks compat. For new APIs, we should use Request/Response pattern (see new APIs at the bottom of the file for examples). For old APIs, we should preserve them for backward compat. The proper cleanup would be to redirect them all to one internal call in metastore imho. Preliminary -1 > Cleanup metastore to put unnecessary parameters in EnvironmentContext > --------------------------------------------------------------------- > > Key: HIVE-12916 > URL: https://issues.apache.org/jira/browse/HIVE-12916 > Project: Hive > Issue Type: Sub-task > Affects Versions: 2.0.0 > Reporter: Pengcheng Xiong > Assignee: Pengcheng Xiong > Priority: Blocker > Attachments: HIVE-12916.01.patch, HIVE-12916.02.patch > > > for example, void alter_table(1:string dbname, 2:string tbl_name, 3:Table > new_tbl) and void alter_table_with_environment_context(1:string dbname, > 2:string tbl_name, 3:Table new_tbl, 4:EnvironmentContext > environment_context), we plan to keep only the latter one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)