[Feature Request]: If I use RAGflow as an external knowledge base, does that mean I can't only use a graph knowledge base for retrieval?

[kou35]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Is your feature request related to a problem?

If I use RAGflow as an external knowledge base, does that mean I can't only use a graph knowledge base for retrieval?

Describe the feature you'd like

If I use RAGflow as an external knowledge base, does that mean I can't only use a graph knowledge base for retrieval?

Describe implementation you've considered

No response

Documentation, adoption, use case

Additional information

No response

[writinwaters]

Knowledge graph is optional. It is an advanced RAG strategy on top of the existing retrieval approaches. In other words, you can skip knowledge graph for retrieval.

[kou35]

Currently, I'm connecting Ragflow as an external knowledge base to Dify, and I have built knowledge graphs in Ragflow. However, I've discovered that when directly connecting Dify to Ragflow, it seems unable to enable the knowledge graph functionality.

[tangyoha]

dify not support config this,but you can use like this

[Reverse-Flash-Kamen]

I use "http://~/retrieval/?use_kg=true&" this api endpoint, but RagFlow can not use knowledge graph currently.

[jionchen]

This will not work, use_kg is in the post request body, placing it in the url will not work.

[Reverse-Flash-Kamen]

This will not work, use_kg is in the post request body, placing it in the url will not work.

Mean that i can use http node in Dify to get RagFlow's knowledge graph?