Member since
02-29-2016
108
Posts
213
Kudos Received
14
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2046 | 08-18-2017 02:09 PM | |
3583 | 06-16-2017 08:04 PM | |
3376 | 01-20-2017 03:36 AM | |
9039 | 01-04-2017 03:06 AM | |
4536 | 12-09-2016 08:27 PM |
02-08-2017
12:20 PM
1 Kudo
I now have a working livy running, at least sc.version works After trying everything I could find with livy 0.2.0 (the version in 2.5.0) I decided to give 0.3.0 a try. I believe that the problem is caused by a bug in spark 1.6.2 when connecting to the metadata store. After compiling livy 0.3.0 with hadoop 2.7.3 and spark 2.0.0, and installing it beside 0.2.0 I had problems creating credentials for the HTTP principal. I solved that by using the hadoop jars from livy 0.2.0 instead of those from the build.
... View more
12-23-2016
04:51 PM
3 Kudos
There was a failure during "Configure Ambari Identity", but retry passed. So I thought it was not really a problem. I am sure the sudo rule is the problem. Will try again and let you know the outcome. Update the sudo permission and got another error: "you must have a tty to run sudo". this turns out to be related to sudo setting, use visudo to comment requiretty fixed the problem visudo
#Defaults requiretty
... View more
06-08-2018
09:58 AM
@Qi Wang Could you please mention the version of Atlas in which the fix has been provided. I am using Atlas 0.8.0 and HDP2.6.4 and I am facing same issue. Could you please help.
... View more
04-28-2017
06:29 PM
5 Kudos
Hi Qi Wang: To your question "I know row level filter only has select. But does it also remove the permission from other policy? Like hive users universal access from the base policy.” --> In this case your user 'hive' has all permissions on all tables through the default access based policy. Also there is a row level policy for user 'hive’ on 'rowfilter' table. We have only ‘select’ privilege to choose in row level policy, what this means is that you are giving user ‘hive’ only ‘select' privilege on the table and that too with restrictions on what he can view on doing ‘select’. Why this is done? If you as a user are not allowed to even see the full contents of a particular table, you cannot be allowed to perform operations on that table. When Hive request comes in from a user, all row level policies are scanned for that user. If a row level policy found for the user, the access privileges are scanned on that resource by going through access policies. (An access policy needs to grant the user access to that resource, row filer policy does not grant access). Now since update is not granted by masking policy, the operation is denied. The request does not even reach access policy. Hope this helps.
... View more
01-07-2017
01:01 AM
Build 35 of HDP 2.5.3 was a near final candidate, but not the final. But good to hear your problem was resolved. Weird.
... View more
11-19-2016
04:27 AM
If you are not able to view the column name in schema tab for hive table, please pull the updated SchemaLayoutView.js from the below jira. https://issues.apache.org/jira/browse/ATLAS-1147
... View more
11-18-2016
04:03 PM
I have not tried this yet, but the link you provide is sufficient for my reference. I was trying to troubleshoot Infra but the underlying problem was fixed after installing Log Search. So it is fine now.
... View more
12-18-2016
06:48 AM
You need a really recent FreeIPA to support --maxlife=0 (https://git.fedorahosted.org/cgit/freeipa.git/commit/?id=d2cb9ed327ee4003598d5e45d80ab7918b89eeed). If you are on supported Redhat or CentOS then you probably you don't have it, unless you rolled your own. You can find out by checking the krbPasswordExpiration attribute of the user. It shouldn't be there. In that case you can try to set it (http://www.therebel.eu/2015/08/setting-password-expiry-in-ipa/) or update your password policy to a lifetime of say 10 years or so (dont go beyond 2038)
... View more
11-07-2016
10:11 PM
1 Kudo
Hi The Hive principal is not a headless principal , ie the hive principal is dedicated to the HiveServer2 Server . So the Principal name always pooints to the Hiveserver2 , which in your case is qwang-hdp2. So if you are able to login using beeline -u "jdbc:hive2://qwang-hdp2:10000/default;principal=hive/qwang-hdp2@REALM.NAME"
Then you are good.
... View more
12-26-2016
04:21 PM
It seems that HDFS is not synching your groups. Try restarting the cluster to see if that helps.
... View more
- « Previous
-
- 1
- 2
- Next »