R transformations are for advanced statistical computations. Apart from ready-to-use implementations of state-of-the-art algorithms, R’s other great assets are vector and matrix computations. R transformations complement Python and SQL transformations where computations or other operations are too difficult. Common data operations like joining, sorting, or grouping are still easier and faster to do in SQL Transformations.
The R script is executed in an isolated environment. The current R version is 4.0.5, however it is possible to switch your configuration to run on other versions if available.
Any updates to the R version is always announced in the Keboola changelog.
An R transformation has a limit of 16GB of allocated memory and the maximum running time is 6 hours. The CPU is limited to the equivalent of two 2.3 GHz processors.
The R script itself will be compiled to
/data/script.R. To access your
mapped input and output tables, use
out/tables/file.csv) or absolute (
To access downloaded files, use the
/data/in/files/ path. If you want to dig really deep,
have a look at the full Common Interface specification.
Temporary files can be written to a
/tmp/ folder. Do not use the
/data/ folder for those files you do not wish to exchange with Keboola Connection.
You can organize your script into blocks, but the resulting R script to be run within our environment must meet the following requirements:
The R transformation can use any package available on
CRAN. In order for a package and
its dependencies to be automatically loaded and installed, list its name in the package section. Using
for loading is not necessary then.
The latest versions of packages are always installed. Some packages are pre-installed in the environment
(see list). These pre-installed packages are
installed with their dependencies, therefore to get an authoritative list of installed packages use the
packages() function. It does no harm if you add one of these packages to your transformation explicitly, but the transformation and
sandbox startup will be slowed by the forced re-installation.
Tables from Storage are imported to the R script from CSV files. The CSV files can be read by standard R functions.
Generally, the table can be read with default R settings. In case R gets confused, use the exact format
sep=",", quote="\"". For example:
Do not include the row index in the output table (use
row.names=FALSE). If you are using the
readr package, you can also use the
which doesn’t write row names.
The row index produces a new unnamed column in the CSV file which cannot be imported to Storage. If the row names contain valuable data, and you want to keep them, you have to convert them to a separate column first.
We have set up our environment to be a little zealous; all warnings are converted to errors and they cause the
transformation to be unsuccessful. If you have a piece of code in your transformation which may emit warnings,
and you really want to ignore them, wrap the code in a
We recommend that you create an R Workspace with the same input mapping your transformation will use. This is the fastest way to develop your transformation code.
Tip: Limit the number of rows you read in from the CSV files:
This will help you catch annoying issues without having to process all data.
To simulate the input and output mapping, all you need to do is create the right directories with the right files. The following image shows the directory structure:
The script itself is expected to be in the
data directory; its name is arbitrary. It is possible to use relative directories,
so that you can move the script to a Keboola Connection transformation with no changes. To develop an R transformation which takes
a sample CSV file locally, take the following steps:
in/tablessubdirectory of the working directory.
in/usersubdirectory of the working directory, and make sure that their name has no extension.
Use this sample script:
A complete example of the above is attached below in data.zip.
Download it and test the script in your local R installation. The
result.csv output file will be created.
This script can be used in your transformations without any modifications.
All you need to do is
source(as expected by the R script),
result.csv(produced by the R script) to a new table in your Storage,
It is possible to output informational and debug messages from the R script simply by printing them out. The following R script:
produces the following events in the transformation job:
app$logError functions are also internally available; they can be useful if you need to know
the precise server time of when an event occurred. The standard event timestamp in job events is the time when the event was received
converted to the local time zone.
The above steps are usually sufficient for daily development and debugging of moderately complex R transformations, although they do not reproduce the transformation execution environment exactly. To create a development environment with the exact same configuration as the transformation environment, use our Docker image.
There are more in-depth examples dealing with