Topology:
|
The storage and analytics
nodes must be on the same machines.
|
Provider:
|
|
Pattern:
|
Symmetric. There must
be a one-to-one mapping between storage and analytics nodes.
|
SASHDAT:
|
In co-located HDFS,
data is staged in SASHDAT format.
|
The HDFS source path in dot-delimited format or the legacy libref.
|
|
Usage:
|
See Administrator Load or use the
data builder.
|
Topology:
|
The storage cluster
can be separate from the analytics cluster.1
|
Provider:
|
MapR. See MapR Distribution for Apache Hadoop in
the SAS LASR Analytic Server: Reference Guide.
|
Pattern:
|
Asymmetric. One-to-one
mapping between storage and analytics nodes is not required.
|
SASHDAT:
|
Data is staged in SASHDAT
format.
|
The NFS source path
in dot-delimited format.
|
|
Usage:
|
See Administrator Load or use the
data builder.
|
1Regardless of topology, the SAS LASR Analytic Server accesses data as if it is co-located. |
Topology:
|
The storage cluster
can be separate from the analytics cluster.
|
Provider:
|
Various.2
|
Pattern:
|
Asymmetric. One-to-one
mapping between storage and analytics nodes is not required.
|
SASHDAT:
|
Data is not staged in
SASHDAT format.
|
Any valid libref.
|
|
Usage:
|
See Administrator Load, use the data
builder, or use an import action.1
|
1Load is parallel if embedded processing is available, LASR table name matches source table name, and server tag is valid as a SAS libref. | |
2See the SAS High-Performance Analytics Infrastructure: Installation and Configuration Guide. |