only the paid version of pinecone works with this (dependency on namespaces)

When did this change? Most of my experimentation with Pinecone was done with the free version.

Same issue here, based on some of the initial documentation and earlier videos it was possible to run on the free Pinecone tier.

GuzzleHttp\Exception\ClientException: Client error: `POST https://drupal10-d6bf3b3.svc.gcp-starter.pinecone.io/vectors/delete` resulted in a `400 Bad Request` response: {"code":3,"message":"The requested feature 'Namespaces' is not supported by the current index type 'Starter'.","details" (truncated...) in GuzzleHttp\Exception\RequestException::create() (line 113 of /app/drupal/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php).

Well thats a bummer. Pinecone and its peers are in trouble with the advancements in OpenAI offering and MySQL/Postgres/Solr etc implementing vector storage and retrieval. But that is another story. I will look into this.

Unfortunately it seems like reworking the code to support free and not free could be a bit of work to cover all the areas, as namespaces used to be required. Is namespace only restricted under querying, or is it not available whatsoever on gcp-starter? If you can't delete records under the free tier anymore that almost seems like a non-starter because that would taint your future vector searches. Is the service really $75 a month?

Maybe adding self identifying config (what subscription tier are you) and then checking that config value in code would be a stop gap, but it might be a bit before I can get to that. Patches welcome.

I think if you leave the namespace empty (and a message: leave empty for no namespace) you could refrain from sending it.
It seems not allowed on any api call (on first sight, not checked on all of them).
The 70 (it was more I think) euro's is what it said on the pricing pages.
But I see that that already changed to some sort of pay as you go pricing.

This makes it work at least - I added a warning about what I understand to be the impact:

• Update hook ensures new disable option is not enabled for existing integrations
• Disable option available in pinecone settings with a warning
• Disabling stops the queue worker from setting a namespace
• Pinecone plugin only adds the namespace arg if its set

Thanks!

LGTM. Thank you!

Thanks!

nice. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.

The starter plan now actually supports namespaces, so will need to get this reverted:
https://docs.pinecone.io/docs/release-notes#december-2023