Tip: In most cases, the source of your data does not limit the type of output that you can generate. You can create a file-based imported dataset and generate results to a database table. Some exceptions may apply.
How to Export
Job results are generated based on the specifications of an output object. An output object is a reference object for one or more types of outputs. This reference information includes full path to the output location, file or table name, and other settings. For more information, see Create Outputs.
In the Run Job page, you can specify additional settings and overrides. See Run Job Page.
Export Job Results
After you have executed a job, the application writes a set of results to the designated output locations. These results are the application of the recipe's transformation steps to the imported dataset, written to the location or locations specified in the output object in the specified output format.
You can export the results directly from the designated output destination. For more information, see Job Details Page.
Tip: Job results for your latest job may be exportable from Flow View. For more information, see View for Outputs.
Writing to Files
As a result of job execution, you can publish your outputs to a file-based system.
NOTE: You must have write permissions to the location where you are writing your output files. These permissions should be set up during initial configuration of the product. For more information, please contact your administrator.
Defaults for file-based outputs:
Files are written to your designated output directory on the backend datastore.
Files are written in CSV format to the designated location.
You can modify the publishing action and generate results in your preferred formats.
- For more information on supported file formats, see Supported File Formats .
In addition to the job results, you can export aspects of the flow definition and other objects that you have created in the Trifacta application. These exports can be useful for:
- Migrating flows to other workspaces
- Archiving data
- Taking snapshots of work in progress
You can export a flow from application. An exported flow is stored in a ZIP file that contains references to all objects needed to use the flow in another workspace or project. Exported flows can be imported into the same workspace/project or a different one.
NOTE: Users of the imported flow must have access to the datasources and specified output locations. If not, these objects must be remapped in the new environment.
For more information, see Export Flow.
You can download a recipe in text form and reuse it in another flows.
Reuse recipes in a different environment
If you need to reuse a recipe in a different instance of Trifacta Wrangler , you can do the following:
- Export the entire flow and import it into the new environment. Open the flow in the new environment. For more information, see Export Flow.
- Convert all steps of a recipe into a macro. Export the macro and then import it into the new environment. For more information, see Export Macro.
You can download recipe in a text form of Wrangle (a domain-specific language for data transformation). For more information, see Recipe Panel .
Export sample data
From the recipe panel, you can download the current state of the data grid, which includes the current sample plus any recipe steps that have been applied to it.
Tip: When a sample is taken, it is tied to the current recipe step. All steps later in the recipe than the current recipe step are computed in memory using the sample as the baseline. For more information, see Overview of Sampling.
F or example, if the sample was generated when the recipe cursor was displaying step 7 and you download the data from the recipe when the recipe cursor is on step 10, then you are downloading the state of the recipe at step 10. For more information, see Recipe Panel .
NOTE: When a flow is shared, its samples are shared with other users. However, if shared users do not have access to the underlying sources that back a sample, they do not have access to the sample. These samples are invalid for the other users, who must create their own.
For more information, see Samples Panel.
This page has no comments.