community: KuzuGraph needs allow_dangerous_requests, add graph documents via LLMGraphTransformer

[prrao87]

• PR title: "community: Kuzu - Add graph documents via LLMGraphTransformer"

  • This PR adds a new method add_graph_documents to use the GraphDocuments extracted by LLMGraphTransformer and store in a Kùzu graph backend.
  • This allows users to transform unstructured text into a graph that uses Kùzu as the graph store.

• 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/

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchain	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 10, 2024 3:15am

[prrao87]

Hi, could I please get an eta on when this could be merged?

cc @baskaryan @eyurtsev

[prrao87]

Hi again, checking in on the status of this PR. Thanks!

cc @vbarda @ccurme

[prrao87]

Trying my luck with @hwchase17. I'd really appreciate it if this PR were reviewed and merged so that Kùzu users who are coming from LangChain can benefit. Cheers!

[alonsosilvaallende]

When can this be merged? Looking forward to it!

[ChuckNoelke]

Hi, when can the merge happen? At my company, we have would like to test it as soon as possible!

[efriis]

hey! given this is very susceptible to sql injection in the relationships objects, would you be open to adding a allow_dangerous_requests: bool flag that is required to be true to the top-level class? Can also add to the add_graph_documents function just for this PR if that makes more sense to you

[prrao87]

Hi @efriis thanks for the response. I think it makes sense to add to the add_graph_documents function as this is the one that actually creates the graph using these f-string queries (I didn't have a choice as the table names need to be constructed dynamically in Kùzu). Could you advise on where the flag can be applied exactly and update this PR? Thanks!

[vercel]

Deployment failed with the following error:

Redirect at index 24 has invalid `source` pattern "/docs/integrations/retrievers/weaviate-hybrid/?".

Learn More: https://vercel.link/invalid-route-source-pattern

[efriis]

ended up doing on the init - it looks like user-provided text can also be passed in query and others, so this can fix across!