Skip to main content

PutVespaDocument

Description

Uses Vespa document api to update a record in a specific namespace.

Tags

embeddings, vector, vespa

Properties

In the list below required Properties are shown with an asterisk (*). Other properties are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Service URL *Service URLThe URL for the Vespa Database
Input Strategy *Input StrategyVespa JSON
  • Vespa JSON
  • Record
The strategy to use to put incoming FlowFiles into Vespa
Record Reader *Record ReaderController Service:
RecordReaderFactory

Implementations:
AvroReader
CEFReader
CSVReader
ExcelReader
GrokReader
JsonPathReader
JsonTreeReader
ReaderLookup
ScriptedReader
Syslog5424Reader
SyslogReader
WindowsEventLogReader
XMLReader
YamlTreeReader
The record reader to use for reading record-oriented data.

This property is only considered if:
  • the property Input Strategy has a value of Record
Document Namespace *Document NamespaceThe Namespace to update with the incoming document FlowFile

Supports Expression Language, using FlowFile attributes and Environment variables.

This property is only considered if:
  • the property Input Strategy has a value of Record
Document Type *Document TypeThe Document Type to update with incoming document FlowFile

Supports Expression Language, using FlowFile attributes and Environment variables.

This property is only considered if:
  • the property Input Strategy has a value of Record
User Defined ID *User Defined ID${filename}The User Defined ID to update with incoming document FlowFile.
The document id will be created using this value and the sequence it appears as a record in the flow file.
The format will be <User Defined Id>_<Record Number>
EX file.json_0

Supports Expression Language, using FlowFile attributes and Environment variables.

This property is only considered if:
  • the property Input Strategy has a value of Record
Communication Timeout *Communication Timeout60 secThe amount of time to wait for a response from the microservices before timing out.

Dynamic Properties

This component does not support dynamic properties.

Relationships

NameDescription
comms.failureIf the processor is unable to communicate with one of the necessary services, the input FlowFile will be routed to this relationship.
failureThe original FlowFile will be routed to this relationship if the document could not be updated
successThe result of a successful document update will be routed to this relationship

Reads Attributes

This processor does not read attributes.

Writes Attributes

This processor does not write attributes.

State Management

This component does not store state.

Restricted

This component is not restricted.

Input Requirement

This component requires an incoming relationship.

System Resource Considerations

This component does not specify system resource considerations.

See Also