hsm207

> Not sure what the best way of differentiating kwargs passed here is, maybe doing some popping from the kwargs so they don't get passed downstream once the client is...

@cs0lar in my opinion, let's wait until that feature makes it to weaviate's official [docs](https://weaviate.io/developers/weaviate/client-libraries/python) to give time for the developers to finalise the interface.

@Pouyanpi > It is the case for all other vectorstores (e.g., faiss, milvus, etc.). Is it possible for you to test it and let me know? [chroma](https://github.com/hwchase17/langchain/blob/b6e3ac17c419acb246e08bf9cd46f3ee0cf2909d/langchain/vectorstores/chroma.py#L385-L395), [pgvector](https://github.com/hwchase17/langchain/blob/b6e3ac17c419acb246e08bf9cd46f3ee0cf2909d/langchain/vectorstores/pgvector.py#L402-L411) and [tair](https://github.com/hwchase17/langchain/blob/b6e3ac17c419acb246e08bf9cd46f3ee0cf2909d/langchain/vectorstores/tair.py#L208-L216)...

can confirm that from_documents works fine now.

from the stack trace, it looks like you have some issue with your machine's ssl config

whoa, that is strange

Why do we want to maintain compatibility with v3 client API?

I'm not a member of the DSPy team (I work at Weaviate). My thoughts are: We recommend [users use the v4 API whenever possible](https://weaviate.io/developers/weaviate/client-libraries/python#python-client-v3-api). Given that this integration is pretty...

i want it 😀

@typefox09 > Can we add the multi tenant logic Weaviate offers also? I opened #13307 to discuss the design Let's open a separate issue for each feature we'd like see...