Re: Need your opinion on HIVE-12916 to clean up metastore API

2016-01-28 Thread Alan Gates
Are you proposing to do this in 2.0 or branch-1 or both? In master we can put up with some backwards incompatibility for now. But given that it's straightforward to maintain it (as Sergey outlines) even there it doesn't seem worth it. So unless there's a very compelling reason (i.e. more

Re: Need your opinion on HIVE-12916 to clean up metastore API

2016-01-25 Thread Sergey Shelukhin
There are 2 separate issues. 1) Removing old APIs. There’s (almost) no impact from keeping the old function for compat if both old and new call the same internal method with slight argument variations, but there would be compact problems with removing them if someone is using it; metastore is

Need your opinion on HIVE-12916 to clean up metastore API

2016-01-25 Thread Pengcheng Xiong
Hi all, I was working on a new feature in HIVE-12730 and I was suggested by Ashutosh to put a configuration in EnvironmentContext. Then I found that we have lots of cases where the configuration and EnvironmentContext both exist in separate functions in the API list. For example, we have