Overview of Storage
The Alteryx Analytics Cloud supports different options for reading and writing data from your storage systems.
Base Storage Layer
The base storage layeris the datastore where the Alteryx Analytics Cloud uploads data, generates profiles, results, and samples. By default, job results are written on the base storage layer. You can configure the base storage layer and other required settings.
Sugerencia
The base storage layer must be a file-based system.
Uses of base storage layer
In general, all base storage layers provide similar capabilities for storing, creating, reading, and writing datasets.
The base storage layer enables you to perform the following functions:
Storing datasets: You can upload or store datasets in directories on the base storage layer. See below.
Creating datasets: You can read in from datasources stored in the storage layer. A source may be a single file or a folder of files.
Storage of samples: Any samples that you generate are stored in the base storage layer.
Ingested data: Some data like Excel and PDF are stored as binary (non-text) files. These files must be read and converted to CSVs, which are stored on the base storage layer.
Cached data: You can enable a cache on the base storage layer, which allows data that has been ingested to remain on the base storage layer for a period of time. This cache allows for faster performance if you need to use the data at a later time.
Writing Results: After you run the job, you can write the results to the storage layer.
Base storage layer directories
The following directories and their sub-directories are created and maintained on the base storage layer:
Directory | Description |
|---|---|
/trifacta/uploads | Storage of datasets uploaded through the Cloud Portal. Directories beneath this one are listed by the internal identifier for each user of the product who has uploaded at least one file. Aviso Avoid using |
/trifacta/queryResults | Default storage of results generated job executions. Directories beneath this one are listed by the internal identifier for each user of the product who has run at least one job. For each user, these sub-directories are the default storage location for job results. These locations can be modified. See Preferences Page. |
/trifacta/dictionaries | Storage of custom dictionary files uploaded by users. Nota This feature applies to only. It is not often used. |
/trifacta/tempfiles | Temporary storage location for files required for use of the product. Nota The |
User-specific directories
The following directories are created by default on the base storage layer for the Alteryx Analytics Cloud to store user data.
By default, these directories are stored in the following:
<bucket_name>/<userId>
where:
<bucket_name>is the name of the bucket where user data is stored.userId>is the username that is used to log in to the product.
Directory | Description |
|---|---|
| Storage of generated samples. |
| Temporary storage |
| Depending on your configuration, uploaded files may be stored in this per-user directory. |
These directories may be modified by individual users. For more information, see Storage Page.
Minimum Permissions
Designer Cloud requires the following operating system level permissions on the listed directories and sub-directories:
Directory | Owner Min Permissions | Group Min Permissions | World Min Permissions |
|---|---|---|---|
/trifacta/uploads | read+write+execute | none | none |
/trifacta/queryResults | read+write+execute | none | none |
/trifacta/dictionaries | read+write+execute | none | none |
/trifacta/tempfiles | read+write+execute | none | none |
Available base storage layers
For information about the Alteryx Analytics Cloud supported base storage layers, see
Nota
In some deployments, the base storage layer is pre-configured for you and cannot be modified. After the base storage layer has been defined, you cannot change it.
Nota
For all storage layers, the source data is untouched. Results are written to a location whenever a job is executed on a source dataset.
Encryption on base storage layer
For data that is transferred to and from the base storage layer:
Data in transit is encrypted using HTTPS.
Data at rest is unencrypted by default.
Management of base storage layer
Maintenance of the base storage layer must be in accordance with your enterprise policies.
Aviso
Unless the base storage layer is managed by Alteryx, it is the responsibility of the customer to maintain access and perform any required backups of data stored in the base storage layer.
Nota
Except for temporary files, the Alteryx Analytics Cloud does not perform any cleanup of the base storage layer.
External Storage
You can create connections to external storage systems. You can integrate the Alteryx Analytics Cloud with an external datastore. Depending on the type of connection and your permissions, the connection can be:
read-only
write-only
read-write
You can create and edit connections between the Alteryx Analytics Cloud and external data stores. You can create either file-based or table-based connections to individual storage units, such as databases or buckets.
Nota
In your environment, creation of connections may be limited to administrators only. For more information, contact your workspace administrator.
Nota
After you create a connection, you cannot change its connection type. You must delete the connection and start again.
File-based systems
In addition to the base storage layer, you may be able to connect to other file-based systems. For example, if your base storage layer is HDFS, you can also connect to S3.
Nota
If HDFS is specified as your base storage layer, you cannot publish to Redshift.
For more information, see Connection Types.
Management of external storage
To integrate with an external system, the Cloud Portal requires:
Basic ability to connect to the hosting node of the external system through your network or cloud-based infrastructure
Requisite permissions to support the browsing, reading and/or writing of data to the storage system
A defined connection between the application and the storage system.
Except for cleanup of temporary files, the Cloud Portal does not maintain external storage systems.