Hi Suzanne, if the Sandbox is in Azure, I am confused about the use of localhost in the command. To access a Sandbox on Azure, I would think you'd need to find the SSH port in Settings > Endpoints (it's set dynamically) and use the publicly-resolvable hostname (as in this guide). Am I missing something about the setup? How are you successfully ssh'ing? ... View more

@Jonathan Kaufman if you are a Hortonworks customer, this would be great detailed information to submit to Support to assist with this issue within your environment. ... View more

Based on the behavior, it seems to be the case that the execution environment for sqoop list-databases is local to the client host and so has access to the user's ticket cache on that host. Sqoop is a wrapper for the creation and submission of MapReduce jobs (and everything here is with respect to MRv2 on YARN). When sqoop import is invoked from the client, resources for the associated Map tasks are allocated by the YARN Resource Manager in the form of YARN containers that are scheduled to run on the cluster's worker nodes. These containers are not forwarded Kerberos tickets, instead they are given delegation tokens (requested by the client and associated with the container's launch context). More details are available here and here. These delegation tokens can be used to access Hadoop resources, such as HDFS, under the authorization context of the client. My speculation is that since the execution context for the Map tasks does not contain the original TGT, this poses an issue for authenticating via Kerberos to services outside of Hadoop that don't interact with Hadoop delegation tokens, like SQL Server. ... View more

@Khera according to this HCC post, Windows Authentication is not yet supported by Sqoop, with the JDBC driver provided by Microsoft, and SQL Authentication must be used. ... View more

@Ravikumar Kumashi please see the --delete-target-dir option for sqoop import. ... View more

@Ravikumar Kumashi please see these docs. By default, Sqoop will import a table named foo to a directory named foo inside your home directory in HDFS. For example, if your username is someuser , then the import tool will write to /user/someuser/foo/(files) . You can adjust the parent directory of the import with the --warehouse-dir argument. For example: $ sqoop import --connnect <connect-str> --table foo --warehouse-dir /shared \ You can also explicitly choose the target directory, like so: $ sqoop import --connnect <connect-str> --table foo --target-dir /dest \ ... View more