Member since
10-19-2015
279
Posts
340
Kudos Received
25
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2270 | 05-12-2017 10:12 AM | |
4056 | 04-03-2017 11:13 AM | |
1217 | 03-28-2017 05:26 PM | |
2720 | 03-06-2017 12:31 PM | |
150627 | 03-02-2017 08:24 AM |
03-28-2017
02:38 AM
EventTime timezone fix is available in Ranger 0.7.0. https://issues.apache.org/jira/browse/RANGER-1249
... View more
03-07-2017
11:59 AM
1 Kudo
It was silly mistake from my side , there was a client truststore file with the same name at server keys location too and i was importing in that file , after importing the certificate to correct file it worked for me thanks!!
... View more
12-02-2017
05:40 PM
@Deepak Sharma in the command "/usr/hdp/current/zookeeper-client/bin/zookeeper-client -server <ZK1>:2181,<ZK2>:2181" <ZK1>:2181,<ZK2>:2181 ---- I dint understand. Could you explain it.
... View more
04-05-2018
12:27 AM
1 Kudo
Pierre solution is correct. If you installed Atlas after Ranger UserSync has been configured to use LDAP, new local users will not get synced in ranger like atlas. This user is needed to setup hbase tables. To fix, revert UserSync to UNIX, restart only Ranger UserSync, Switch back to UserSync LDAP config. In Ranger add user atlas to HBase all policy. Restart Atlas.
... View more
02-23-2017
01:32 PM
Hi Ayub, thanks a lot for your help. It worked 🙂
... View more
02-10-2017
01:49 PM
Sorry guys, that was the issue. Not only me have access to that cluster, and somebody changed ranger policy url in every plugin config. Thank you!
... View more
12-07-2016
09:58 PM
1 Kudo
ah it needed an account on the hadoop2 server since hiveserver2 is running there. I created 'sami' on hadoop2 and added it to the hadoop group and then I can use hive using my ticket.
... View more
11-22-2017
05:34 AM
Hi, This issue was resolved by the settings as follows: hadoop.proxyuser.root.hosts=* You can also see the answer on the below comment. https://community.hortonworks.com/comments/144449/view.html
... View more
12-06-2016
06:26 PM
Glad you have it worked out. Somehow I missed your last post stating that it is already installed, so my previous comment is OBE.
... View more
11-11-2016
09:55 AM
2 Kudos
If the cluster is kerberized only one user can create new topic with command: bin/kafka-topics.sh --create --zookeeper <you zk node> --replication-factor 1 --partitions 1 --topic kafka_topic
This user is the user who runs the kafka broker, this is a zookeeper security limitation but there is a property in kafka auto.create.topics.enable, if this one is set to true the required topic will be created if the user produce/consume message. bin/kafka-console-producer.sh --broker-list broker address --topic kafka_topic --security-protocol SASL_PLAINTEXT
This command will create the kafka_topic, with different users.
... View more