removed get_knowledge_graph

[YanSte]

Description

• removed get_knowledge_graph never implemented everywhere

Changes Made

• removed get_knowledge_graph method

Checklist

• Changes tested locally
• Code reviewed

[YanSte]

Only for mango and neo4j so no needed

[ArnoChenFx]

No! It's used by the WebUI. Every graph backend should implement the get_knowledge_graph interface.

#737 #792

LightRAG/lightrag_webui/src/api/lightrag.ts

Lines 164 to 167 in cbc5d9d

	export const queryGraphs = async (label: string): Promise<LightragGraphType> => {
	const response = await axiosInstance.get(`/graphs?label=${label}`)
	return response.data
	}

LightRAG/lightrag_webui/src/hooks/useLightragGraph.tsx

Lines 53 to 61 in cbc5d9d

	const fetchGraph = async (label: string) => {
	let rawData: any = null
	try {
	rawData = await queryGraphs(label)
	} catch (e) {
	useBackendState.getState().setErrorMessage(errorMessage(e), 'Query Graphs Error!')
	return null
	}

@YanSte

[YanSte]

@ArnoChenFx Sorry I just got you message..

[YanSte]

But @ArnoChenFx get_knowledge_graph is not implemented in Oracle and others, that will crash.

[YanSte]

Again sorry for that @ArnoChenFx Will fallback this implementation.

[ArnoChenFx]

@LarFii said he would implement the get_knowledge_graph for networkx. The get_knowledge_graph for neo4j existed before I wrote the webui, and the get_knowledge_graph for mongo was written by me using AI. Sorry, I don't have the ability to implement get_knowledge_graph for other backends.

[LarFii]

@LarFii said he would implement the get_knowledge_graph for networkx. The get_knowledge_graph for neo4j existed before I wrote the webui, and the get_knowledge_graph for mongo was written by me using AI. Sorry, I don't have the ability to implement get_knowledge_graph for other backends.

Yes. Once I finish handling my graduation-related tasks, I will prioritize implementing the get_knowledge_graph.