Thanks Kevin. When you said "Knox with Hive requires HiveServer2 in HTTP mode", does it mean once this mode is activated some connections might be not able to connect to HS2? Would a user be able to bypass Knox by using an old Hive CLI (no beeline based) even if HS2 is using the latest Hive version with Hive CLI wrapping beeline?
Thanks. On Wed, 13 Mar 2019 at 17:08, Kevin Risden <[email protected]> wrote: > I'm not sure which version exactly but this is the umbrella jira tracking > all the subtasks: > > https://issues.apache.org/jira/browse/HIVE-10511 > > Kevin Risden > > > On Wed, Mar 13, 2019 at 1:04 PM Odon Copon <[email protected]> wrote: > >> Amazing, thanks Kevin for the clarification. >> Do you know exactly which version did the transition to beeline? >> >> On Wed, 13 Mar 2019 at 16:53, >> Kevin Risden >> <[email protected]> wrote: >> >>> Knox with Hive requires HiveServer2 in HTTP mode. Hive CLI direct to >>> metastore is not supported by Knox. Current versions of Hive as far as I >>> know have Hive CLI wrapping beeline by default for SQL queries. >>> >>> Kevin Risden >>> >>> >>> On Wed, Mar 13, 2019 at 12:49 PM Odon Copon <[email protected]> wrote: >>> >>>> After reading Knox documentation I'm not totally sure how Knox can sit >>>> in front of Hive accesses through JDBC/Beeline and Hive CLI. >>>> From the docs, I see it does for JDBC connections so I assume it does >>>> for Beeline as well, as both hit HiveServer2, but what about Hive CLI that >>>> go directly to the Hive Metastore?. >>>> Thanks. >>>> >>>
