For smaller datasets, the Transformer page displays the entire dataset. For larger ones, the source data is sampled for use in the Transformer page.
At the top of the Transformer page, the type of the current sample is displayed next to the dataset name. To open the Samples panel, click the link. In the example below, the Full Data link indicates that the current sample in the Transformer page is the entire dataset:
Click the Samples link.
The Samples panel is displayed on the right side of the screen:
At the top of the panel, you can review the currently loaded sample. Each user has his own active sample on a dataset.
NOTE: When a new sample is generated, any Sort transformations that have been applied previously must be re-applied. Depending on the type of output, sort order may not be preserved.
Initial: By default, the application loads the first N rows of the dataset as the initial sample when the Transformer page is opened. The number of rows depends on column count, data density, and other factors. If the dataset is small enough, the full dataset is used.
NOTE: By default, samples may be up to 10 MB in size. For datasets smaller than this limit, the entire dataset is loaded.
Click the link in the current sample card to see the list of all available samples.
Tip: To change the name of a sample, click its card in the list of all available. Then, click the Edit icon.
Below the current sample, you can review the available options for creating new samples. Each type of sample reflects a different method of collection.
To collect a new sample, click the appropriate sample card. See below.
NOTE: If a sample fails to generate, you can retry or downloadlogs for review. Click the Download Logs link. These logs may be useful in debugging.
At the bottom of the Transformer page, you can review the number of rows and columns and count of data types in the currently displayed sample.
NOTE: As you add transformation steps to your recipe, the values in the status bar change to reflect the current state of the loaded sample.
NOTE: Some operations, such as
When a new sample is collected, it is gathered based on the current location in the recipe when the sample is gathered. So, if the recipe contains steps that join in other datasets, those joins are performed to bring together the data from which the sample is executed.
Collect new sample panel
NOTE: Except for the initial sample, all samples are generated based on the steps leading up to the location of the cursor in the recipe. If earlier steps are deleted or modified, the collected sample can be invalidated.
NOTE: When sampling from compressed data, the source is uncompressed, and a new sample of it is loaded into the data grid. As a result, the sample size you see in the grid corresponds to the uncompressed data.
Name: You can enter a new name of the sample as needed.
Tip: Naming your samples can assist in tracking them later. For example, you might choose to add a date stamp to the name to track when you captured the sample.
Quick- performs a random scan of the dataset to extract the appropriate number of rows for the sample
Full- gathers the sample from the entire dataset. Depending on the size of the dataset, this method can take a while.
Use latest data: When collecting a Full Scan sample from a JDBC source and performance ingest caching has been enabled, you can choose to override the cached data and to gather all of your data from the original sources.
NOTE: If the cached data has expired, the sample is always collected from the original sources, even if this option is not selected.
Click more details to review the list of datasets whose cached data will be overridden.
Ingest caching applies to non-native relational (JDBC) sources. For more information, see Configure JDBC Ingestion.
Condition: (Filter-based, Stratified, Cluster-based, Anomaly-based) Filter the sample based on a specified condition. For example:
invoiceDate > 90
In the Collected samples panel, you can review the available and unavailable samples. If applicable, you can review the variable override values that were applied during the sampling.
To use one of the available samples, select its card. The sample is loaded in the data grid.
NOTE: If you add recipe steps that change the number of rows in your dataset (or a few other edge case steps), some of your existing samples may no longer be valid. When you execute a join, union, or delete action or edit steps before this action, you may be prompted with the Change Recipe dialog, which includes the following message:
Your change will invalidate some of the currently available samples for this source. The invalid samples will be deactivated.
For more information on the types of transformations that can invalidate samples, see Reshaping Steps.