Member since
07-19-2018
613
Posts
101
Kudos Received
117
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5689 | 01-11-2021 05:54 AM | |
| 3812 | 01-11-2021 05:52 AM | |
| 9491 | 01-08-2021 05:23 AM | |
| 9295 | 01-04-2021 04:08 AM | |
| 38639 | 12-18-2020 05:42 AM |
05-09-2020
05:24 AM
@michaelli Not from the UI. You will need to go back to the actual metastore server and see the command(s) to create the hive user. If it’s a MySQL metastore it’s easy to go to MySQL prompt and arrow up to see previously executed commands with the hive user and password.
... View more
05-06-2020
04:51 PM
1 Kudo
@Udhav you will need to create permissions for the user to access the table you create in the metastore. Underlying cause: java.sql.SQLException : Access denied for user 'hive'@'localhost' (using password: YES) SQL Error code: 1045 For example mysql: CREATE DATABASE hive; CREATE USER 'hive'@'localhost' IDENTIFIED BY 'hive'; GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost' WITH GRANT OPTION; FLUSH PRIVILEGES; In Ambari Admin Hive Config Database tab and during Cluster Instal Wizard for Hive, there should be a Test Connection button for Hive Metastore. Use this feature to test the connection during install. Also just to make sure, there is also a requirement for mysql-connector for ambari: To use MySQL with Hive, you must download the https://dev.mysql.com/downloads/connector/j/ from MySQL. Once downloaded to the Ambari Server host, run: ambari-server setup --jdbc-db=mysql --jdbc-driver=/path/to/mysql/com.mysql.jdbc.Driver If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
04-29-2020
06:27 AM
@abhinav_joshi In NiFi you can have all kinds of different processors from different versions. The preferred procedure is to put them in a custom-libs folder location available to nifi(s), add a value to nifi config, delete the work directory in nifi(s), and restart nifi(s). You can see more info about how I did this on the following post: https://community.cloudera.com/t5/Support-Questions/Can-I-put-the-NiFi-1-10-Parquet-Record-Reader-in-NiFi-1-9/m-p/289111#M214056
... View more
04-28-2020
05:15 AM
@Damian_S You cannot delete and recreate a hadoop cluster in this manner. The data in the metastore is very specific to the previous installation. A proper migration will back up the required artifacts from the original cluster, and migrate them to a new existing ambari cluster that has already completed the initial cluster installation.
... View more
04-28-2020
05:09 AM
@san_re The configuration of Remote Url in InvokeHTTP should be as follows: /j_security_check?j_username=${j_username}&j_password=${j_password} Notice the credential values are passed to the url with the ?. This is the only change in the processor config. Here is a demo flow: GenerateFlowFile - starts flow for testing UpdateAttribute - sets user, pass,and mime type attributes needed in InvokeHttp InvokeHttp - sends POST You can find this template on my GitHub to inspect the entire flow: https://github.com/steven-dfheinz/NiFi-Templates/blob/master/InvokeHttp_Demo.xml
... View more
04-22-2020
11:59 AM
Here is Ambari 2.7.4 (last of the repos before moved behind paywall) main link for Repos: https://docs.cloudera.com/HDPDocuments/Ambari-2.7.4.0/bk_ambari-installation/content/ch_obtaining-public-repos.html When you get the right 2.7.4 repos you will be able to install in Ubuntu 18.
... View more
04-22-2020
11:42 AM
What repo did you add to your ubuntu server? Share your history if you can. HDP 3 should have repos for ubuntu 18: https://docs.cloudera.com/HDPDocuments/Ambari-2.7.5.0/bk_ambari-installation/content/hdp_315_repositories.html
... View more
04-22-2020
05:11 AM
@Udhav Yes. Once you complete the rest of the node readiness (install repos, ambari-server, ambari-agent) you would visit http://[fqdn]:8080 and begin rest of cluster install via Ambari.
... View more
04-22-2020
04:26 AM
@Udhav You need to set the hostname to the fqdn (not localhost), map the hostname in /etc/hosts/, generate the ssh-keys, add keys to authorized_keys, and login. Thats it. Here is full output of the above steps. Please note the vagrant vm I use already has ssh setup, but I did it again (you will notice 2 keys in authorized_keys). [root@c7401 ~]# hostname c7401.ambari.apache.org [root@c7401 ~]# hostname -f c7401.ambari.apache.org [root@c7401 ~]# cat /etc/hosts | grep c7401 192.168.74.101 c7401.ambari.apache.org c7401 [root@c7401 ~]# ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. [root@c7401 ~]# cat ~/.ssh/id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDbUBYPL9JcoThQ5HWjZLpaHPEd3UlQaPcxzs1p08+pmWc6Q8JT+SGJ4G9087sDMnO1HsutzaoRchlTVN8AN1p7bg9mSnUVGYBSfrmz9dNiYujBCmEnymEB2qn30u3YncFE8um+fQRafrkcMTGwTfclB1CU9mP4FZEIW0+fWBqHBnR3mmkaVUAUgVATLTKIw8dMngDTRG9zVS6HVEpMPQYXl6mK5Oq0XLq31AZpYb7Fia4plw2mK7wQLUxxc0dSa7NQ3bzvr+lO3LRzEaAVvk4ZlqXddX23Z8PpsX7ZhS8lnQn4sojH82+BndVUO9N8VzS3LxzSAjmAThEDC47eXQyV root@c7401.ambari.apache.org [root@c7401 ~]# cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys [root@c7401 ~]# cat ~/.ssh/authorized_keys ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDbUBYPL9JcoThQ5HWjZLpaHPEd3UlQaPcxzs1p08+pmWc6Q8JT+SGJ4G9087sDMnO1HsutzaoRchlTVN8AN1p7bg9mSnUVGYBSfrmz9dNiYujBCmEnymEB2qn30u3YncFE8um+fQRafrkcMTGwTfclB1CU9mP4FZEIW0+fWBqHBnR3mmkaVUAUgVATLTKIw8dMngDTRG9zVS6HVEpMPQYXl6mK5Oq0XLq31AZpYb7Fia4plw2mK7wQLUxxc0dSa7NQ3bzvr+lO3LRzEaAVvk4ZlqXddX23Z8PpsX7ZhS8lnQn4sojH82+BndVUO9N8VzS3LxzSAjmAThEDC47eXQyV root@c7401.ambari.apache.org [root@c7401 ~]# ssh root@c7401.ambari.apache.org The authenticity of host 'c7401.ambari.apache.org (192.168.74.101)' can't be established ECDSA key fingerprint is SHA256:mjGym7gkqWjPvW2JXhKjqWl4XC6wuhgNIukldSVtkFk. ECDSA key fingerprint is MD5:b7:d4:73:92:03:69:ae:63:af:69:19:96:51:2b:bc:de. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'c7401.ambari.apache.org,192.168.74.101' (ECDSA) to the list of known hosts. Last login: Wed Apr 22 11:21:57 2020
... View more