NOTE: For more information on support for Azure with this release, please contact your .
This section describes how you interact through the with your WASB environment.
The can use WASB for the following tasks for reading and writing data:
In the , WASB is accessed through the WASB browser. See WASB Browser.
NOTE: When the executes a job on a dataset, the source data is untouched. Results are written to a new location, so that no data is disturbed by the process.
Read/Write Access: Your HDInsight administrator must configure read/write permissions to locations in WASB. Please see the WASB documentation provided with your HDInsight distribution.
NOTE: If a directory is created on the HDI cluster through WASB, the directory includes a Size=0 blob. The does not list them and does not support interaction with Size=0 blobs.
Your HDInsight administrator should provide a place or mechanism for raw data to be uploaded to your HDInsight datastore.
Your HDInsight administrator should provide a writeable home output directory for you. This directory location is available through your user profile. See User Profile Page.
Client-side encryption is not supported. Through WASBS, HTTPS is supported.
Your HDInsight administrator should provide raw data or locations and access for storing raw data within WASB. All should have a clear understanding of the folder structure within WASB where each individual can read from and write their job results.
NOTE: The does not modify source data in WASB. Data stored in WASB is read without modification from source locations, and source data that is uploaded to the platform are stored in
You can import a dataset from one or more files stored in WASB.
You can parameterize your input paths to import source files as part of the same imported dataset. For more information, see Overview of Parameterization.
When you select a folder in WASB for your imported dataset, you select all files in the folder to be included. Notes:
*_FAILEDfiles, which may be present if the folder has been populated by Hadoop.
_), these files cannot be read during batch transformation and are ignored. Please rename these files through WASB so that they do not begin with an underscore.
When creating a dataset, you can choose to read data in source data stored from WASB or from a local file.
/trifacta/uploadswhere they remain and are not changed.
Data may be individual files or all of the files in a folder.
When your job results are generated, they can be stored back in WASB at the location defined for your user account.
If your deployment is using WASB, do not use the
As part of writing job results, you can choose to create a new dataset, so that you can chain together data wrangling tasks.
NOTE: When you create a new dataset as part of your job results, the file or files are written to the designated output location for your user account. Depending on how your WASB permissions are configured, this location might not be accessible to other users.