Documentation

Write to Vertica

To write data to Vertica with Flux:

  1. Import the sql package.

  2. Pipe-forward data into sql.to() and provide the following parameters:

    • driverName: vertica or vertigo
    • dataSourceName: See data source name
    • table: Table to write to
    • batchSize: Number of parameters or columns that can be queued within each call to Exec (default is 10000)
import "sql"

data
    |> sql.to(
        driverName: "vertica",
        dataSourceName: "vertica://username:password@localhost:5433/dbname",
        table: "public.example_table",
    )

Vertica data source name

The vertica and vertigo drivers use the following DSN syntax (also known as a connection string):

vertica://<user>:<password>@<host>:<port>/<database>?<queryArgs>

The vertica and vertigo drivers use the vertica/vertica-sql-go implementation. For information about supported DSN query arguments, see the vertica/vertica-sql-go documentation.

Flux to Vertica data type conversion

sql.to() converts Flux data types to Vertica data types.

Flux data typeVertica data type
floatFLOAT
intINTEGER
uintINTEGER
stringVARCHAR
boolBOOL
timeTIMESTAMP

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2