I believe the ans lies here:
http://www.cloudera.com/content/cloudera-content/cloudera-docs/Impala/latest/Installing-and-Using-Impala/ciiu_cm_installation.html
Let me know if it's not covered here.
Thanks,
Alan
On Fri, Sep 5, 2014 at 11:34 AM, ml wrote:
If anyone running Impala has a few minutes and can let me know what their
install is like on a Cloudera Manager installation of Impala that would be
helpful. What i'm interested in is the binary/directory permissions. I've
read a few posts that mention it needing to be installed explicitly as the
Impala user for it to execute the hdfs actions as that user. Does that mean
a separate rpm db(CentOS) for that user? Any info that might point me in
the right direction would be great...
Thanks
To unsubscribe from this group and stop receiving emails from it, send an email to impala-user+unsubscribe@cloudera.org.If anyone running Impala has a few minutes and can let me know what their
install is like on a Cloudera Manager installation of Impala that would be
helpful. What i'm interested in is the binary/directory permissions. I've
read a few posts that mention it needing to be installed explicitly as the
Impala user for it to execute the hdfs actions as that user. Does that mean
a separate rpm db(CentOS) for that user? Any info that might point me in
the right direction would be great...
Thanks
On Wednesday, September 3, 2014 10:20:04 AM UTC-7, ml wrote:
Hi, thanks for your reply. That is actually not the behavior as i
understand it. Impala submits all queries as a single user and cannot do
impersonation at this time. Sentry is currently required for handling
authorization with impiala-shell if i understand the documentation
correctly.
For what it's worth, i increased logging on the daemon and see that it
identifies the user correctly but when it actually executes the commands
against hdfs it runs that as root... example:
This is the log output executing impala-shell on a gateway machine as the
impala user itself (recognizes the impala user correctly):
01: query (string) = "create database impalatestdb location
'/impalatest/testdb'",
03: configuration (list) = list<string>[0] {
},
04: hadoop_user (string) = "impala",
}
...
Output of a create database statement in impala-shell:
ERROR: ImpalaRuntimeException: Error making 'createDatabase' RPC to Hive
Metastore:
CAUSED BY: MetaException: Got exception: org.apache.hadoop.security.AccessControlException
Permission denied: user=root, access=WRITE, inode="/impalatest/"
...
...
The permissions are set correctly on that path so that the root user
should not be able to write to it. The problem is that this command should
be running as the impala user and not root.
I obviously have something setup incorrectly but i'm not able to pin down
what is causing this.
Thanks
an email to impala-user+unsubscribe@cloudera.org.Hi, thanks for your reply. That is actually not the behavior as i
understand it. Impala submits all queries as a single user and cannot do
impersonation at this time. Sentry is currently required for handling
authorization with impiala-shell if i understand the documentation
correctly.
For what it's worth, i increased logging on the daemon and see that it
identifies the user correctly but when it actually executes the commands
against hdfs it runs that as root... example:
This is the log output executing impala-shell on a gateway machine as the
impala user itself (recognizes the impala user correctly):
01: query (string) = "create database impalatestdb location
'/impalatest/testdb'",
03: configuration (list) = list<string>[0] {
},
04: hadoop_user (string) = "impala",
}
...
Output of a create database statement in impala-shell:
ERROR: ImpalaRuntimeException: Error making 'createDatabase' RPC to Hive
Metastore:
CAUSED BY: MetaException: Got exception: org.apache.hadoop.security.AccessControlException
Permission denied: user=root, access=WRITE, inode="/impalatest/"
...
...
The permissions are set correctly on that path so that the root user
should not be able to write to it. The problem is that this command should
be running as the impala user and not root.
I obviously have something setup incorrectly but i'm not able to pin down
what is causing this.
Thanks
On Tuesday, September 2, 2014 5:43:10 PM UTC-7, Alan wrote:
Hi ml,
If you log in as user "A" and start impala-shell, Impala shell will send
"A" as the user to Impala. So, if you log in as root, the query will be
executed as "root".
Thanks,
Alan
Hi ml,
If you log in as user "A" and start impala-shell, Impala shell will send
"A" as the user to Impala. So, if you log in as root, the query will be
executed as "root".
Thanks,
Alan
On Fri, Aug 29, 2014 at 10:48 AM, ml wrote:
I've tried several different things but there doesn't seem to be a way
to change the user the queries execute as. Is there something hard-coded in
the binary somewhere? Can you all point me in any direction that might be
able to help me figure this out? Thanks.
To unsubscribe from this group and stop receiving emails from it, sendI've tried several different things but there doesn't seem to be a way
to change the user the queries execute as. Is there something hard-coded in
the binary somewhere? Can you all point me in any direction that might be
able to help me figure this out? Thanks.
On Thursday, August 28, 2014 2:05:14 PM UTC-7, ml wrote:
OK, I've upgraded to 1.4.0 and unfortunately I'm still seeing all
queries run as root. The impalad processes however are running as the
impala user on the nodes.
On Wednesday, August 20, 2014 11:06:49 PM UTC-7, Ippokratis Pandis
wrote:
send an email to impala-user...@cloudera.org.OK, I've upgraded to 1.4.0 and unfortunately I'm still seeing all
queries run as root. The impalad processes however are running as the
impala user on the nodes.
On Wednesday, August 20, 2014 11:06:49 PM UTC-7, Ippokratis Pandis
wrote:
Hi,
I think you can upgrade to 1.4 without problems. Having said that, I
don't think that upgrading metastore will require you to change any
schema.
Regards,
-Ippokratis.
from:
docs/Impala/latest/Cloudera-Impala-Version-and-Download-
Information/Cloudera-Impala-Version-and-Download-Information.html
up to
possible.
it, send
--
-Ippokratis.To unsubscribe from this group and stop receiving emails from it, send an
email to impala-user...@cloudera.org.
--
-Ippokratis.
To unsubscribe from this group and stop receiving emails from it,I think you can upgrade to 1.4 without problems. Having said that, I
don't think that upgrading metastore will require you to change any
schema.
Regards,
-Ippokratis.
On Wed, Aug 20, 2014 at 1:14 PM, ml wrote:
What version of hive metastore schema is required with impala 1.4? I
currently run hive 0.10 so I want to make sure that it will work with the
version of the metastore schema i have.
Thanks
On Tuesday, August 19, 2014 4:56:42 PM UTC-7, Ippokratis Pandis
wrote:What version of hive metastore schema is required with impala 1.4? I
currently run hive 0.10 so I want to make sure that it will work with the
version of the metastore schema i have.
Thanks
On Tuesday, August 19, 2014 4:56:42 PM UTC-7, Ippokratis Pandis
Hi,
You can download the latest rpms (1.4.0) that work with CDH 4
You can download the latest rpms (1.4.0) that work with CDH 4
docs/Impala/latest/Cloudera-Impala-Version-and-Download-
Information/Cloudera-Impala-Version-and-Download-Information.html
Regards,
-Ippokratis.
-Ippokratis.
On Tue, Aug 19, 2014 at 4:55 PM, ml wrote:
I am on cdh4 and don't think 1.4 is available for it. I can get
I am on cdh4 and don't think 1.4 is available for it. I can get
1.2.4
i believe but i'd like to sort this issue out first if at all
i believe but i'd like to sort this issue out first if at all
thanks.
To unsubscribe from this group and stop receiving emails from
To unsubscribe from this group and stop receiving emails from
an
email to impala-user...@cloudera.org.
email to impala-user...@cloudera.org.
--
-Ippokratis.
email to impala-user...@cloudera.org.
--
-Ippokratis.
