# Vertica Bulk Loader

## <img src="/files/xEcRgaXZr8DJO0f1GhFF" alt="" data-size="line"> Vertica Bulk Loader

The Vertica Bulk Loader uses [VerticaCopyStream](https://www.vertica.com/docs/12.0.x/HTML/Content/Authoring/ConnectingToVertica/ClientJDBC/UsingVerticaCopyStream.htm) to stream to a Vertica database.

This is typically significantly faster than loading data through e.g. a Table Output transform.

| Hop Engine | <sup>✓</sup> |
| ---------- | ------------ |
| Spark      | ?            |
| Flink      | ?            |
| Dataflow   | ?            |

### Options

#### Global transform options

| Option                  | Description                                                                                                                               |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Transform name          | Name of the transform.                                                                                                                    |
| Connection              | Name of the database connection on which the target table resides.                                                                        |
| Target schema           | The name of the Schema for the table to write data to. This is important for data sources that allow for table names with dots '.' in it. |
| Target table            | Name of the target table.                                                                                                                 |
| Truncate table          | Truncate this table before loading data                                                                                                   |
| Truncate on first row   | Only truncate this table if there is data (when the first row is received)                                                                |
| Specify database fields | Enable this option to specify the fields in the Database fields tab. Otherwise all fields are taken into account by default.              |

#### Main options tab

| Option                 | Description                                                                                                                                  |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Insert directly to ROS | Insert directly to ROS (Read Optimized Store). A ROS (Read Optimized Store) container is a set of rows stored in a particular group of files |
| Abort on error         | Stop or continue loading data as soon as an error occurs                                                                                     |
| Exceptions log file    | Path to the exceptions log file                                                                                                              |
| Reject data log file   | Path to the rejected data log file                                                                                                           |
| Stream name            | Name for the Vertica COPY stream                                                                                                             |

#### Database fields tab

Map table columns to stream fields using 'Get Fields' and/or 'Enter Field Mapping'.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/verticabulkloader.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.