[
https://issues.apache.org/jira/browse/HIVE-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864981#comment-15864981
]
Greg Senia commented on HIVE-10511:
-----------------------------------
[~gopalv] thank you for further insight. I wish all Hadoop Vendors I talked
with felt the same way. I know multiple vendors who feel Hive and HiveServer2
should be the ONLY access mechanism on top of Hadoop. I guess the approach
we've been taking at my current and past employer is that tools like Voltage or
Protegrity or Dataguise would be used to secure column level access using FPE.
But I can see how some companies would not want to invest down that road. How
is LLAP and doAS working is that going to work as things like Protegrity
require jobs to run as the actual endUser. It cannot run as Hive and
unfortunately I don't think this requirement will be changing any time soon.
> Replacing the implementation of Hive CLI using Beeline
> ------------------------------------------------------
>
> Key: HIVE-10511
> URL: https://issues.apache.org/jira/browse/HIVE-10511
> Project: Hive
> Issue Type: Bug
> Components: CLI
> Affects Versions: 0.10.0
> Reporter: Xuefu Zhang
> Assignee: Ferdinand Xu
>
> Hive CLI is a legacy tool which had two main use cases:
> 1. a thick client for SQL on hadoop
> 2. a command line tool for HiveServer1.
> HiveServer1 is already deprecated and removed from Hive code base, so use
> case #2 is out of the question. For #1, Beeline provides or is supposed to
> provides equal functionality, yet is implemented differently from Hive CLI.
> As it has been a while that Hive community has been recommending Beeline +
> HS2 configuration, ideally we should deprecating Hive CLI. Because of wide
> use of Hive CLI, we instead propose replacing Hive CLI's implementation with
> Beeline plus embedded HS2 so that Hive community only needs to maintain a
> single code path. In this way, Hive CLI is just an alias to Beeline at either
> shell script level or at high code level. The goal is that no changes or
> minimum changes are expected from existing user scrip using Hive CLI.
> This is an Umbrella JIRA covering all tasks related to this initiative. Over
> the last year or two, Beeline has been improved significantly to match what
> Hive CLI offers. Still, there may still be some gaps or deficiency to be
> discovered and fixed. In the meantime, we also want to make sure the enough
> tests are included and performance impact is identified and addressed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
