NiFi Ingest 25.4
NiFi Ingest

# PutVertica

Indexes documents into a Vertica database.

## Properties

Name | Default Value | Description
--- | --- | ---
IDOL License Service |  | An IdolLicenseServiceImpl that provides a way to communicate with a Knowledge Discovery License Server.
Vertica Connection string |  | The connection string to use to connect to the Vertica database.
Vertica Table Name |  | The name of the table in the Vertica database to index the documents into. The table must be a flex table and must already exist.
- Field Format | CSV | Specifies how to send the value of a document field to Vertica when the field has more than one value. CSV - Send the values as a string, comma-separated list.
      {
        field : "value1,value2,value3"
      }
- Array - Send the values as a JSON array.
      {
        field : ["value1","value2","value3"]
      }
- Mixed - Send a single value as a string, multiple values as an array.
      {
        field : ["value1","value2","value3"]
        field2 : "value"
      }
Field Structure | Flattened | Specifies how to send subfield and field attribute data to Vertica. Flattened - The information is flattened. Nested - Attributes and subfields are represented as nested JSON objects. Use this mode to preserve the original structure of your documents. Documents can have multiple fields with the same name. Sending information in nested mode means that it is possible to see which field a sub-field or attribute was attached to.
SSL Config Service |  | An optional IdolSSLConfigServiceImpl that specifies the settings to use to index documents over an encrypted connection.
Document Registry Service |  | A DocumentRegistryServiceImpl controller service that manages and updates a document registry database. This ensures that documents are indexed in the correct order.
Indexer Batch Size | 100 | The maximum number of FlowFiles to accumulate before indexing documents. Indexing documents in larger batches can be more efficient; indexing smaller batches more frequently means that an individual document might spend less time in the queue. Documents might be indexed in incomplete batches if the Indexing Interval Duration is reached first.
Indexing Interval Duration | 5 min | The maximum amount of time to wait between indexing batches of documents. Documents might be indexed more frequently than this if the Indexer Batch Size is reached first. Waiting longer and indexing documents in larger batches can be more efficient; indexing smaller batches more frequently means that an individual document might spend less time in the queue.

## Relationships

Name | Description
--- | ---
success | FlowFiles that were indexed successfully.
failure | FlowFiles that were not indexed successfully.

Copyright 2018-2025 Open Text
Version 25.4 | Last updated October 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery NiFi Ingest 25.4

Topic Title: PutVertica