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.

Uses of WASB

The  can use WASB for the following tasks for reading and writing data:

  1. Importing datasets from WASB Files: You can read in from source data stored in WASB. An imported dataset may be a single WASB file or a folder of identically structured files. See Reading from Sources in WASB below.
  2. Reading Datasets: When creating a dataset, you can pull your data from a source in WASB. See Creating Datasets below.
  3. Writing Results: You can publish your results directly to WASB. See Writing Job Results below.
  4. Publishing Job Results: After a job has been executed, you can write the results back to WASB. See Writing Job Results below.

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.

Before You Begin Using WASB

Secure Access

Client-side encryption is not supported. Through WASBS, HTTPS is supported.

Tip: WASBS protocol is recommended for accessing the datastore.

Storing Data in WASB

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 /trifacta/uploads.

Reading from Sources in WASB

You can import a dataset from one or more files stored in WASB. When you select a folder in WASB for your imported dataset, you select all files in the folder to be included. Notes:

Creating Datasets

When creating a dataset, you can choose to read data in source data stored from WASB or from a local file.

Data may be individual files or all of the files in a folder.

Writing Job Results

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 trifacta/uploads directory. This directory is used for storing uploads and metadata, which may be used by multiple users. Manipulating files outside of the can destroy other users' data. Please use the tools provided through the interface for managing uploads from WASB.

Creating a new dataset from results

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.