Pinecone

Since Camel 4.6

Only producer is supported

The Pinecone Component provides support for interacting with the Pinecone Vector Database.

URI format

pinecone:collection[?options]

Where collection represents a named set of points (vectors with a payload) defined in your database.

Configuring Options

Camel components are configured on two separate levels:

  • component level

  • endpoint level

Configuring Component Options

At the component level, you set general and shared configurations that are, then, inherited by the endpoints. It is the highest configuration level.

For example, a component may have security settings, credentials for authentication, urls for network connection and so forth.

Some components only have a few options, and others may have many. Because components typically have pre-configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.

You can configure components using:

  • the Component DSL.

  • in a configuration file (application.properties, *.yaml files, etc).

  • directly in the Java code.

Configuring Endpoint Options

You usually spend more time setting up endpoints because they have many options. These options help you customize what you want the endpoint to do. The options are also categorized into whether the endpoint is used as a consumer (from), as a producer (to), or both.

Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.

A good practice when configuring options is to use Property Placeholders.

Property placeholders provide a few benefits:

  • They help prevent using hardcoded urls, port numbers, sensitive information, and other settings.

  • They allow externalizing the configuration from the code.

  • They help the code to become more flexible and reusable.

The following two sections list all the options, firstly for the component followed by the endpoint.

Component Options

The Pinecone component supports 4 options, which are listed below.

Name Description Default Type

configuration (producer)

The configuration;.

PineconeVectorDbConfiguration

lazyStartProducer (producer)

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

boolean

token (producer)

Sets the API key to use for authentication.

String

autowiredEnabled (advanced)

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

boolean

Endpoint Options

The Pinecone endpoint is configured using URI syntax:

pinecone:collection

With the following path and query parameters:

Path Parameters (1 parameters)

Name Description Default Type

collection (producer)

Required The collection Name.

String

Query Parameters (2 parameters)

Name Description Default Type

token (producer)

Sets the API key to use for authentication.

String

lazyStartProducer (producer (advanced))

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

boolean

Message Headers

The Pinecone component supports 13 message header(s), which is/are listed below:

Name Description Default Type

CamelPineconeAction (producer)

Constant: ACTION

The action to be performed.

Enum values:

  • CREATE_COLLECTION

  • CREATE_INDEX

  • UPSERT

  • INSERT

  • SEARCH

  • DELETE

  • UPDATE

  • QUERY

  • QUERY_BY_ID

String

CamelPineconeTextFieldName (producer)

Constant: TEXT_FIELD_NAME

Text Field Name for Insert/Upsert operation.

String

CamelPineconeVectorFieldName (producer)

Constant: VECTOR_FIELD_NAME

Vector Field Name for Insert/Upsert operation.

String

CamelPineconeIndexName (producer)

Constant: INDEX_NAME

Index Name.

String

CamelPineconeIndexPodType (producer)

Constant: INDEX_POD_TYPE

Index Pod Type.

String

CamelPineconeIndexPodEnvironment (producer)

Constant: INDEX_POD_ENVIRONMENT

Index Pod Environment.

String

CamelPineconeCollectionName (producer)

Constant: COLLECTION_NAME

Collection Name for Insert/Upsert operation.

String

CamelPineconeCollectionSimilarityMetric (producer)

Constant: COLLECTION_SIMILARITY_METRIC

Collection Similarity Metric.

Enum values:

  • cosine

  • euclidean

  • dotproduct

String

CamelPineconeCollectionDimension (producer)

Constant: COLLECTION_DIMENSION

Collection Dimension.

int

CamelPineconeCollectionCloud (producer)

Constant: COLLECTION_CLOUD

Collection Cloud Vendor.

Enum values:

  • aws

  • gcp

  • azure

String

CamelPineconeCollectionCloudRegion (producer)

Constant: COLLECTION_CLOUD_REGION

Collection Cloud Vendor Region.

Enum values:

  • aws

  • gcp

  • azure

String

CamelPineconeIndexId (producer)

Constant: INDEX_ID

Index Upsert Id.

String

CamelPineconeQueryTopK (producer)

Constant: QUERY_TOP_K

Query Top K.

Integer

Spring Boot Auto-Configuration

When using pinecone with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:

<dependency>
  <groupId>org.apache.camel.springboot</groupId>
  <artifactId>camel-pinecone-starter</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel core version -->
</dependency>

The component supports 5 options, which are listed below.

Name Description Default Type

camel.component.pinecone.autowired-enabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

Boolean

camel.component.pinecone.configuration

The configuration;. The option is a org.apache.camel.component.pinecone.PineconeVectorDbConfiguration type.

PineconeVectorDbConfiguration

camel.component.pinecone.enabled

Whether to enable auto configuration of the pinecone component. This is enabled by default.

Boolean

camel.component.pinecone.lazy-start-producer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

Boolean

camel.component.pinecone.token

Sets the API key to use for authentication.

String
Back to top