I hope you don't mind me cc'ing user-group so that this q&a is
available for others as well.

The grant/revoke based authorization models (including the new
sql-standards based authorization in hive 0.13) does not automatically
ensure that the user has necessary privileges on hdfs dirs and files.
To have this model work with hdfs, the usual strategy is to have all
users go through hiveserver2. HiveServer2 is configured with
hive.server2.doAs=false, and then you give permissions on hdfs to the
user hiveserver2 is running as.
On Sun, Jun 15, 2014 at 8:27 PM, Apple Wang <[EMAIL PROTECTED]> wrote:

NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB