Using the Hadoop HDFS_TEMPDIR= LIBNAME option in a Hadoop environment secured by Kerberos might produce a misleading error. 

When you connect to a Hadoop cluster that is secured by Kerberos, the HDFS_TEMPDIR= location is checked before actually assigning the LIBNAME statement. If a valid Kerberos ticket does not exist or the ticket has expired, the LIBNAME connection fail with an error message similar to the following in the SAS^® log.   

Even though the location specified in the HDFS_TEMPDIR option might physically exist, the error occurs because the LIBNAME statement fails. As a result, the HDFS_TEMPDIR location cannot be accessed.  

The above error message does not indicate which error might have occurred so that information is not documented in the SAS log. Removing the HDFS_TEMPDIR= option from the LIBNAME statement allows the underlying connection error to be written to the SAS log. The following "GSS initiate failed" error indicates that a valid Kerberos ticket does not exist:

You should assign the Hadoop LIBNAME statement without the HDFS_TEMPDIR= option to verify whether Java Database Connectivity (JDBC) is successful. When the LIBNAME statement is successfully assigned and the HDFS_TEMPDIR= option is necessary to redirect temporary files, add the option to the LIBNAME statement.  

A fix for this issue is planned for a future release.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Hadoop 9.45 is available at:

A fix for this issue for SAS/ACCESS Interface to Hadoop 9.44 is available at: