It would seem that there shouldn't be an issue doing a different binding for Hive 3 as well as hive 4 if there is that much difference. It would allow the Hive 2 one to be maintained and could eventually be EOL'd once it becomes not useful. This sort of pattern can be used across multiple version of almost anything there is a Sentry binding for.
On Mon, Aug 27, 2018 at 11:09 AM Kalyan Kumar Kalvagadda <kkal...@cloudera.com.invalid> wrote: > Sergio, > > We could add profiles for to multiple version of Hive till the point we > want to support multiple versions. We should also consider supporting > Hadoop-3 as well. > We could take similar approach to support multiple versions of Hadoop as > well. > > > On Mon, Aug 27, 2018 at 10:22 AM Sergio Pena > <sergio.p...@cloudera.com.invalid> wrote: > > > Hi All, > > > > I'd like to discuss how we can start integrating Apache Hive 3.x and > future > > 4.x into our Sentry versions. I've noticed that Hive has released two > > versions of 3.x this year (3.0 on May/18, 3.1 on Jul/18), and the current > > version development is 4.0. > > > > Currently, Sentry supports only the Hive 2.x, and there is no news of new > > minor versions on that line to be released in the community. However, > there > > are still companies using the Hive 2.x version due to its stability and > API > > compatibility. Also, I see a lot of incompatibilities problems once Hive > > 4.0 is released too. > > > > So, the question, how can we keep with the most updated Hive releases but > > being compatible with Hive versions that are still active by the Sentry > > community? Btw, Hive 3.x has features that allow Sentry support ALTER > TABLE > > SET OWNER commands to transfer object ownership. > > > > Hive had a shims interface for Hadoop to support Hadoop 1.x and Hadoop > 2.x > > in the past. Should we use a similar thing? > > > > Any other ideas? > > > > - Sergio > > > -- *Brian Towles* | Software Engineer t. (512) 415- <0000000000>8105 e. btow...@cloudera.com <j...@cloudera.com> cloudera.com <http://www.cloudera.com/> [image: Cloudera] <http://www.cloudera.com/> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera on LinkedIn] <https://www.linkedin.com/company/cloudera> ------------------------------
