...
| Tip |
|---|
Tip: Where possible, you should make selections in the data grid to build transform steps. These selections prompt a series of cards to be displayed at the bottom of the screen. You can select different cards to specify a basic transform for your selected data, choose a variant of that transform, and then modify the underlying recipe as necessary. For more information, see Overview of Predictive Transformation.For more information on the suggestion cards, see Selection Details Panel. Some complex transforms, such as joins and unions, must be created through dedicated screens. See Transformer Page. |
vs. SQL| Info |
|---|
NOTE: is not SQL. It is a proprietary language of data transformation, purpose-built for . |
While there are some overlaps between
and SQL, here are the key distinctions:- is a proprietary language designed for data transformation. Every supported transformation is designed to make changes to a dataset. It cannot be used to read from or write to a datastore.
- Users interact with exclusively through the . There is no direct interaction with the language.
- SQL (Structured Query Language) is designed for querying, transforming, and writing for relational datasources. It cannot be applied to file-based datasets.
- SQL cannot be used to transform data in .
| Tip |
|---|
Tip: Optionally, you can enable and use SQL to perform custom queries of your relational datasources. These read-only queries can be used only to import data into the product. For more information, see Enable Custom SQL Query. |
Syntax
transforms follow this general syntax:
...
