Problem Note 70503: Bulk load might fail when you use Cloudera Data Services (CDS) and connect to a Virtual Warehouse via SAS/ACCESS® Interface to Hadoop
A failure occurs when you connect to a Virtual Warehouse using LDAP authentication and the underlying HDFS instance is configured with Kerberos. The reason for the failure is because SAS® attempts to write to HDFS using the authentication method specified in the LIBNAME.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After installing the hot fix, set the SAS_HADOOP_HDFS_AUTH_TYPE environment variable to KERBEROS. With this setting in place, you can make the LIBNAME connection to Hive using USERID/PASSWORD authentication and connect to HDFS using Kerberos.
You can set the environment variable in the SAS code by entering the following before the LIBNAME statement:
options set=SAS_HADOOP_HDFS_AUTH_TYPE="KERBEROS";
In addition, you can set the environment variable for all SAS sessions in the !SASROOT/bin/sasenv_local file on Unix SAS installs or as a system environment variable on a Windows SAS installation.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Hadoop | Microsoft® Windows® for x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8 Enterprise 32-bit | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8 Enterprise x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8 Pro 32-bit | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8 Pro x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Enterprise x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Pro 32-bit | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Pro x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 10 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows 11 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 R2 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 for x64 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 Datacenter | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 R2 Std | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 Std | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2016 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2019 | 9.48 | | 9.4 TS1M8 | |
Microsoft Windows Server 2022 | 9.48 | | 9.4 TS1M8 | |
Windows 7 Enterprise 32 bit | 9.48 | | 9.4 TS1M8 | |
Windows 7 Enterprise x64 | 9.48 | | 9.4 TS1M8 | |
Windows 7 Home Premium 32 bit | 9.48 | | 9.4 TS1M8 | |
Windows 7 Home Premium x64 | 9.48 | | 9.4 TS1M8 | |
Windows 7 Professional 32 bit | 9.48 | | 9.4 TS1M8 | |
Windows 7 Professional x64 | 9.48 | | 9.4 TS1M8 | |
Windows 7 Ultimate 32 bit | 9.48 | | 9.4 TS1M8 | |
Windows 7 Ultimate x64 | 9.48 | | 9.4 TS1M8 | |
64-bit Enabled AIX | 9.48 | | 9.4 TS1M8 | |
64-bit Enabled Solaris | 9.48 | | 9.4 TS1M8 | |
Linux for x64 | 9.48 | | 9.4 TS1M8 | |
Solaris for x64 | 9.48 | | 9.4 TS1M8 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-11-14 11:22:26 |
Date Created: | 2023-11-10 11:26:07 |