community: Add Zep Cloud components + docs + examples #21671
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
bot
added
size:XXL
|
Looking into linter errors |
|
@baskaryan Our Cloud APIs have diverged from Open Source, both from an API and functionality perspective. The API will likely be harmonized soon, but the functionality will stay differentiated. We have two sets of SDKs as a result. We don't want to break the existing components for the open source users. |
| try: | ||
| from zep_cloud import MemorySearchResult, SearchScope, SearchType | ||
| from zep_cloud.client import AsyncZep, Zep | ||
|
|
||
| class ZepCloudRetriever(BaseRetriever): | ||
| """`Zep Cloud` MemoryStore Retriever. |
There was a problem hiding this comment.
this type of definition will prevent this class from being properly documented in the API reference. Would it be better to just remove the typing from the pydantic attributes (eg zep_client: Any instead of zep_client: Zep)?
There was a problem hiding this comment.
Roger that, addressed. Also did the same for async client.
There was a problem hiding this comment.
sorry should've been clearer, we need to remove the class definition from the try/except clause for it to be documented
There was a problem hiding this comment.
@baskaryan my bad, removed the try/except clause.
…ud-components # Conflicts: # libs/community/tests/unit_tests/vectorstores/test_public_api.py
dosubot
bot
added
the
lgtm
Thank you for contributing to LangChain!
- [x] **PR title**: community: Add Zep Cloud components + docs +
examples
- [x] **PR message**:
We have recently released our new zep-cloud sdks that are compatible
with Zep Cloud (not Zep Open Source). We have also maintained our Cloud
version of langchain components (ChatMessageHistory, VectorStore) as
part of our sdks. This PRs goal is to port these components to langchain
community repo, and close the gap with the existing Zep Open Source
components already present in community repo (added
ZepCloudMemory,ZepCloudVectorStore,ZepCloudRetriever).
Also added a ZepCloudChatMessageHistory components together with an
expression language example ported from our repo. We have left the
original open source components intact on purpose as to not introduce
any breaking changes.
- **Issue:** -
- **Dependencies:** Added optional dependency of our new cloud sdk
`zep-cloud`
- **Twitter handle:** @paulpaliychuk51
- [x] **Add tests and docs**
- [x] **Lint and test**: Run `make format`, `make lint` and `make test`
from the root of the package(s) you've modified. See contribution
guidelines for more: https://python.langchain.com/docs/contributing/
Additional guidelines:
- Make sure optional dependencies are imported within a function.
- Please do not add dependencies to pyproject.toml files (even optional
ones) unless they are required for unit tests.
- Most PRs should not touch more than one package.
- Changes should be backwards compatible.
- If you are adding something to community, do not re-import it in
langchain.
If no one reviews your PR within a few days, please @-mention one of
baskaryan, efriis, eyurtsev, hwchase17.
Thank you for contributing to LangChain!
PR title: community: Add Zep Cloud components + docs + examples
PR message:
We have recently released our new zep-cloud sdks that are compatible with Zep Cloud (not Zep Open Source). We have also maintained our Cloud version of langchain components (ChatMessageHistory, VectorStore) as part of our sdks. This PRs goal is to port these components to langchain community repo, and close the gap with the existing Zep Open Source components already present in community repo (added ZepCloudMemory,ZepCloudVectorStore,ZepCloudRetriever).
Also added a ZepCloudChatMessageHistory components together with an expression language example ported from our repo. We have left the original open source components intact on purpose as to not introduce any breaking changes.
zep-cloudAdd tests and docs
Lint and test: Run
make format,make lintandmake testfrom the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/Additional guidelines:
If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.