API Migration

[david-oplatka]

Description

We have switched all of the backend implementation for the Vectara Managed Index from using Vectara's API v1 to API v2. This adds new functionalities, such as allowing new parameters to be specified when indexing documents into Vectara Managed Index or when making queries to one or multiple corpora. This also changes the credentials required to set up the index and connect to the Vectara API.

However, this also has breaking changes with the current implementation. These have all been documented in a new Changelog.md file for Vectara Managed Index. Additionally, all README, documentation, and example notebooks have been updated to reflect the new implementation and demonstrate how to appropriately use this updated version.

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes

Type of Change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

I added new tests for existing and new functions to the test files for Vectara Managed Index and Vectara Query Tool and all ran successfully.

• I added new unit tests to cover this change

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran make format; make lint to appease the lint gods

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[logan-markewich]

Neat! Huge change -- thanks for tackling this