Pinecone Integration avatar
Pinecone Integration

Pricing

Pay per usage

Go to Store
Pinecone Integration

Pinecone Integration

Developed by

Apify

Apify

Maintained by Apify

This integration transfers data from Apify Actors to a Pinecone and is a good starting point for a question-answering, search, or RAG use case.

3.8 (6)

Pricing

Pay per usage

34

Total users

396

Monthly users

85

Runs succeeded

95%

Issues response

5.7 hours

Last modified

2 months ago

OB

MetadataDatasetFields mapping doesn't support array of fields for combining multiple source fields

Open

obscur0x opened this issue
7 months ago

When trying to combine multiple source fields into a single metadata field using an array syntax in metadataDatasetFields, the Actor fails with the error: "'list' object has no attribute 'split'".

Current behavior:

  • Single field mapping works: "address": "ubicationAddress" successfully maps the field
  • Combined fields fail: "address": ["ubicationAddress", "address"] throws an error
  • Alternative syntax "address": "ubicationAddress, address" results in empty field

Expected behavior:

  • Should be able to combine multiple source fields into a single metadata field using array syntax
  • Example: "address": ["ubicationAddress", "address"] should combine both fields into the address metadata field

This functionality would be useful for cases where we need to combine multiple fields from the source data into a single metadata field, such as combining street address with location data.

Steps to reproduce:

  1. Set up an Actor with metadata mapping
  2. Configure metadataDatasetFields with array syntax:
{
"metadataDatasetFields": {
"address": ["ubicationAddress", "address"]
}
}
jiri.spilka avatar

Hi, thank you for your interest in the Pinecone integration!

And thank you for providing excellent explanations and examples. As you’ve discovered, this functionality is not currently supported. I agree that this combination could be useful in certain cases, but a similar result can be achieved using two fields:

{
"metadataDatasetFields": {
"ubicationAddress": "ubicationAddress",
"address": "address"
}
}

Why can't you use two fields in metadata?

Using your suggested syntax might complicate the setup, and it would only allow for a simple concatenation.

This is the first request for this kind of field combination. I’ve copied this issue to GitHub as a "nice-to-have" feature.