Find answers from the community

Updated 7 months ago

Recursive retriever llamaparse and qdrant

@Logan M is this true?
s
L
5 comments
I’m also getting this error when using llamaparse and qdrant. My worry is if I convert the node ids that I’ll lose the ability to do recursive retriever engine?
{
  "error": "Unexpected Response: 400 (Bad Request)\nRaw response content:\nb'{"status":{"error":"Format error in JSON body: value id_13305a9d-46f9-4539-8be5-8c981b759141_0_table_ref is not a valid point ID, valid values are either an unsigned integer or a UUID"},"time":0.0}'"
}
Depends on how you set it up

If your recursive stuff is serializable, you can just index it directly.

For example
https://github.com/run-llama/llama_parse/blob/main/examples/demo_advanced.ipynb
This is fixed if you update core (I think, either that or it's in the next release, qdrant is silly and requires uuid for node ids)
Ok great so as long as I just pass the node and objects to qdrant we’re good, I just converted the node ids to uuid for now is that going to break the table/node etc relationships in llamaparse?

And lastly I’m trying to use llamaparse with gcsreader and getting a fs error llamaparse wasn’t expecting it?

Thank you Logan! 😊
Nah that's fine, that's a good workaround

And I don't think fs is supported just yet on llamaparse (there's a pr that I need to finish merging)
Add a reply
Sign up and join the conversation on Discord