Tags: pinecone-io/pinecone-java-client
Tags
Prepare to release v5.1.0 (#191) ## Problem Prepare to release v5.1.0 ## Solution Update CHANGELOG.md and pineconeClientVersion in gradle.properties and constants.java. ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [X] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan NA
Generate code for 2025-04, automate ndjson handling, add backups, res… …tore, and namespaces. (#183) ## Problem 1. Generate code for 2025-04 and automate ndjson handling. 2. Add support for backups and restore. 3. Add support for namespaces ## Solution 1. Generated code using the 2025-04 open api spec and added sed command to automate the process of handling ndjson which is currently not handled by the open api genearted code in ApiClient.java of data.yaml module. 2. Added support for backups and restore 3. Added support for namespaces ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [ ] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan Integration tests were added for new features.
Generate code for 2025-04, automate ndjson handling, add backups, res… …tore, and namespaces. (#183) ## Problem 1. Generate code for 2025-04 and automate ndjson handling. 2. Add support for backups and restore. 3. Add support for namespaces ## Solution 1. Generated code using the 2025-04 open api spec and added sed command to automate the process of handling ndjson which is currently not handled by the open api genearted code in ApiClient.java of data.yaml module. 2. Added support for backups and restore 3. Added support for namespaces ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [ ] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan Integration tests were added for new features.
Prepare to release v4.0.1 (#179) ## Problem Prepare to release v4.0.1 ## Solution Releasing a patch version requires updating: - gradle.properties - CHANGELOG.md - Constants.java ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [X] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan NA
Update rerank example in the README after breaking changes (#177) ## Problem Rerank endpoint is updated to accept documents as List<Map<String, Object>> instead of List<Map<String, String>> and parameters now accepts Map<String, Object> instead of Map<String, String>. ## Solution Update the example in README for rerank example ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [X] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan NA
Prepare for releasing v3.0.0 (#165) ## Problem Prepare for releasing Java SDK v3.0.0. ## Solution Releasing a major version requires updating: 1. README 2. gradle.properties 3. CHANGELOG.md 4. Constants.java ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update - [ ] Infrastructure change (CI configs, etc) - [X] Non-code change (docs, etc) - [ ] None of the above: (explain here) ## Test Plan No code is updated as a part of this change, integration tests should run as expected.
Prep for release v2.1.0 and add proxy config & disabling TLS examples… … to README (#152) ## Problem - Prepare for releasing v2.1.0. - Added support proxy configuration and for disabling TLS, so add examples to the README. ## Solution - Update pinecone client version to `v2.1.0`. - Add proxy config and disabling TLS examples to README ## Type of Change - [X] Non-code change (docs, etc) ## Test Plan NA
PreviousNext