fix(tugraph_store.py): _create_schema crash

[tpoisonooo]

Description

Fix tugraph creation error

How Has This Been Tested?

Here is my KG result

Checklist:

• My code follows the style guidelines of this project
• I have already rebased the commits and make the commit message conform to the project standard.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules

[Appointat]

@tpoisonooo Thanks so much for your PR.

Issue: when GraphRAG builds the DB schema, different versions of TuGraph handle the types STRING and "STRING" differently (one version supports STRING; while the other version supports "STRING"). It is caused by the TuGraph version update.

We fixed it in another PR (document structure search in GraphRAG), and will release it in the next released version of DB-GPT.

Solutions: We used statements createVertexLabelByJson and createEdgeLabelByJson to be compatible with the new and old versions of feat. (note: createVertexLabelByJson and createEdgeLabelByJson have not yet been updated in the official documentation of TuGraph)

            gql_data = json.dumps({
                "label": graph_elem_type.value,
                "type": "EDGE",
                "constraints": edge_direction(graph_elem_type),
                "properties": graph_properties,
            })
            gql = f"""CALL db.createEdgeLabelByJson('{data}')"""

Related issue [closed]: #2073

[csunny]

@tpoisonooo Thanks for your contribution, we already fix this issue in another PR #2033 and will add you as a co-contributor about this issue #2073

[Appointat]

@tpoisonooo could you provide me your email?, so that I can add you to the contributors of pr #2033 (reply to me today if possible). :)

[Appointat]

@tpoisonooo you were added to the co-author of pr #2033. Thank you.
I think this pr can be closed now. : )