SPD Server Restrictions on Hadoop

The SPD Server COPY and LOAD statements in SQL explicit pass-through are not supported in a Hadoop domain. The commands require local direct access to the source and destination tables from the machine on which the server is running.

An implicit pass-through using the CREATE TABLE AS SELECT statement to SPD Server does not support creating a Hadoop table that already exists. That is, a table on a Hadoop cluster cannot be replaced using implicit pass-through. If a table exists, SPD Server fails a query with a Member Lock error. This results in PROC SQL planning and executing the query, which causes the selected rows to be read from SPD Server to SAS. The selected rows are returned to SPD Server to create the table.

A best practice is to drop the table before creating it.

SPD Server does not support user-defined formats in a Hadoop domain. User-defined formats require a record-level locking proxy, but the Hadoop file system locking mechanisms do not support this operation.

The following SPD Server options are not supported for a Hadoop domain:

By default, the SPD Server user password file is located in the InstallDir/site directory. If you do not keep the file in this location, you must specify the location using the ACLDIR start-up option, which is explained in the SAS Scalable Performance Data Server: Administrator’s Guide. The location for the user password file must be on the local file system, not HDFS. This restriction exists for the following reasons: