This section provides an overview of exporting data from the to your preferred destinations, such as file-based storage, connected datastores, or your desktop. In addition to exporting of job results, other types of exports are covered in this section.
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.
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.
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.
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. As needed, you can modify your default output directory. For more information, see Storage Page.
Files are written in CSV format to the designated location.
You can modify the publishing action and generate results in your preferred formats.
You can export generated results directly to a connected relational database.
Tip: Some relational connection types support read-only or write-only connections.
The writes results to a database through an object called a connection. A connection is a configuration object that defines the interface between the application and the database. Among its properties are a set of credentials that provide access.
NOTE: You must have write permissions to the database where you are writing your output tables. These permissions must be enabled by a database administrator outside of the product.
NOTE: Connections can be shared among users. When a user chooses to share a connection, the user can also choose to share credentials. If credentials are not shared, other users must provide their own credentials if they wish to use the connection. For more information, see Share a Connection.
For relational databases, the passes the information in the connection definition to a third-party driver that performs the actual connection. Thereafter, the maintains the open connection as long as it is needed to write results. After the results are written, the connection is closed.
When you choose to write results to a table:
Additional options may be available, depending on the connection. For more information, see Relational Table Settings.
For file-or table-based publishing actions, you can parameterize elements of the output path. You can create parameters for your outputs of the following types:
Variable: Variable parameters allow you to insert values that you define as part of the output object.
Tip: You can optionally override the values of your variable parameters as part of your job definition.
For more information on parameters, see Overview of Parameterization.
After a job has successfully completed, you can review and download the set of generated outputs and export results. Optionally, you may be able to publish the generated results to a secondary datastore through the Job Details page.
NOTE: Additional configuration may be required.
For more information on ad-hoc publishing, see Publishing Dialog.
In addition to the job results, you can export aspects of the flow definition and other objects that you have created in the . These exports can be useful for:
You can export a flow from . 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.
If you need to reuse a recipe in a different instance of , you can do the following:
You can download recipe in a text form of . For more information, see Recipe Panel.
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.
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.
After a job has run, you can acquire the path to the results when you query for the job. For more information, see