Update data

This page shows you how to use the update operation to update parts of existing records in an index namespace. To update entire records, use the upsert operation instead.

​

Update dense vector values

In this example, assume you want to update the dense vector values of the following record in the example-namespace namespace: ("id-3", [3.0, 3.0], {"type": "doc", "genre": "drama"}).

After the update, the dense vector values are changed, but the metadata is unchanged: ("id-3", [4.0, 2.0], {"type": "doc", "genre": "drama"}).

​

Update metadata values

When updating metadata, only the specified metadata fields are modified, and if a specified metadata file does not exist, it is added.

In this example, assume you are updating the metadata values of following record in the example-namespace namespace:

(id="id-3", values=[4.0, 2.0], metadata={"type": "doc", "genre": "drama"}).

After the update, the type metadata field is web, the new property is added with the value true, and the genre property is unchanged:

(id="id-3", values=[4.0, 2.0], metadata={"type": "web", "new": true, "genre": "drama"}).

​

Update sparse vector values

In this example, assume you are updating the sparse vector values of the following record in the example-namespace namespace:

(
	id="id-3", 
	values=[1.0, 2.0], 
	sparse_values={"indices": [1, 5], "values": [0.5, 0.5]}
)

After the update, the sparse value indices array is changed, but the rest of the record is unchanged:

(
	id="id-3", 
	values=[1.0, 2.0], 
	sparse_values={"indices": [2, 6], "values": [0.5, 0.5]}
)

​

Update a combination of values

In this example, assume you are updating the dense vector values and one metadata value of the following record in the example-namespace namespace:

(id="id-3", values=[4.0, 2.0], metadata={"type": "doc", "genre": "drama"}).

After the update, the dense vector values and the genre metadata value would be changed, but the type metadata value would be unchanged: (id="id-3", values=[5.0, 3.0], metadata={"type": "doc", "genre": "comedy"}).

​

Data freshness

Pinecone is eventually consistent, so there can be a slight delay before new or changed records are visible to queries. You can use the describe_index_stats operation to check data freshness.