, The CLUSTERED BY clause is used to divide the table into buckets. Rows with the same bucketed column will always be stored in the same bucket. In this case, even though there are 50 possible states, the rows in this table will be clustered into 32 buckets. The SORTED BY clause keeps the rows in each bucket ordered by one or more columns. This does not enforce global ordering across buckets for the whole table, only local ordering within each bucket, as each bucket is physically a separate file in the table directory. If the tables being joined are bucketized on the join columns, and the number of buckets in one table is a multiple of the number of buckets in the other table, the buckets can be joined on the map-side. Map-side joins on bucketed tables will be faster - as the mapper processing a bucket of the left table knows that the matching rows in the right table will be in their corresponding bucket, so it doesn't need to scan the whole table. Map-side joins on tables with sorted by buckets are even more efficient, as the join boils down to just merging the already sorted buckets. A more detailed explanation, along with MapJoin restrictions, can be found here: https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Joins. ... View more

In your /etc/network/interfaces file, you probably have something like the following: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp In your /etc/network/interfaces file, you need to change the inet element under eth0 to static and add your desired networking info: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.78.10 netmask 255.255.255.0 network 192.168.78.0 broadcast 192.168.78.255 gateway 192.168.78.1 The first three elements of your address, network, broadcast, and gateway should be the same as those in the ip automatically assigned by vmware to your vm (in this case, 192.168.178). The fourth element of your address should be something between 3 and 128 inclusive, to avoid conflicts with dhcp (in this case 10). The fourth element of network is always 0. The fourth element of broadcast is always 255. The fourth element of gateway is always 1. Finally, be sure to restart your vm for the above changes to take effect and then follow the steps in our doc to check DNS and NSCD. ... View more

run hostname -f from the command line on the sandbox vm, and you should see the following: [root@sandbox ~]# hostname -f sandbox.hortonworks.com So, assuming you are running sqoop from the same sandbox vm, this fqdn should resolve properly. You can cat the contents of /etc/hosts/ to verify: [root@sandbox ~]# cat /etc/hosts # File is generated from /usr/lib/hue/tools/start_scripts/gen_hosts.sh # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 192.168.59.103 sandbox.hortonworks.com sandbox ambari.hortonworks.com If you are running the sqoop command from another host, then you need to make sure the second entry in the sandbox /etc/hosts file is in the /etc/hosts file on that host as well. Before running the sqoop command, you can test that you can connect to mysql using that hostname from the command line: [root@sandbox ~]# mysql -h sandbox.hortonworks.com -u root Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 71 Server version: 5.1.73 Source distribution Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> If that command works, then the jdbc connection with the same hostname, username, and password will work. ... View more

Ambari uses hostnames as keys for all managed hosts. You can follow the steps to customize the name of your host in Ambari. In the future, I'd recommend using custom hostnames under your own public domain, but following these steps on the new hosts should get you out of the bind you are in. Ambari presently does not support changing hostnames dynamically. There is a Jira open for this,https://issues.apache.org/jira/browse/AMBARI-4670. But current trunk has no support for it. ... View more