Documentation

Query Vertica

To query Vertica with Flux:

  1. Import the sql package.

  2. Use sql.from() and provide the following parameters:

    • driverName: vertica or vertigo
    • dataSourceName: See data source name
    • query: PSQL query to execute
import "sql"

sql.from(
    driverName: "vertica",
    dataSourceName: "vertica://username:password@localhost:5433/dbname",
    query: "SELECT * FROM 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.

Vertica to Flux data type conversion

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

Vertica data typeFlux data type
INT, INTEGER, BIGINT, SMALLINT, TINYINT, INT2, INT4, INT8, SERIAL2, SERIAL4, SERIAL8int
FLOAT, FLOAT4, FLOAT8float
DATE, TIME, TIMESTAMPtime
BOOLbool
TEXT, VARCHAR, VARBINARYstring

All other Vertica data types are converted to strings.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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