There have been a number of changes to the OpenAPI spec including renaming of tags, inclusion of the List endpoint. We need to regenerate and replace pinecone-generated-ts-fetch.
Solution
Regenerate /pinecone-generated-ts-fetch off of the most current OpenAPI spec. Everything under /pinecone-generated-ts-fetch is auto-generated and can be ignored.
Rename VectorOperationsProvider -> DataOperationsProvider to keep things consistent. We moved away from "vector" terminology previously and since our OpenAPI tags have changed this felt like a good time to update our client naming.
Bonus query integration test changes:
The query integration test was taking a while to run, and we were seeing failures when trying to delete records which don't actually exist (I think the server started throwing 404s for this recently where they failed silently previously? Which was a bug in one of the tests, so it was useful for catching this). I cleaned up the integration test to only seed record data beforeAll, and clean up afterAll, so we no longer have to wait for records to be ready in each test which will save us quite a bit of time overall in this test. (I think between 1-2 minutes for each test run).
Type of Change
[X] New feature (non-breaking change which adds functionality)
Test Plan
There are no changes to client functionality in this PR. All unit tests, builds, and integration tests should pass as expected in CI.
Problem
There have been a number of changes to the OpenAPI spec including renaming of tags, inclusion of the List endpoint. We need to regenerate and replace
pinecone-generated-ts-fetch.Solution
/pinecone-generated-ts-fetchoff of the most current OpenAPI spec. Everything under/pinecone-generated-ts-fetchis auto-generated and can be ignored.VectorOperationsProvider->DataOperationsProviderto keep things consistent. We moved away from "vector" terminology previously and since our OpenAPI tags have changed this felt like a good time to update our client naming.Bonus
queryintegration test changes:queryintegration test was taking a while to run, and we were seeing failures when trying to delete records which don't actually exist (I think the server started throwing 404s for this recently where they failed silently previously? Which was a bug in one of the tests, so it was useful for catching this). I cleaned up the integration test to only seed record databeforeAll, and clean upafterAll, so we no longer have to wait for records to be ready in each test which will save us quite a bit of time overall in this test. (I think between 1-2 minutes for each test run).Type of Change
Test Plan
There are no changes to client functionality in this PR. All unit tests, builds, and integration tests should pass as expected in CI.