The community member is having an issue with the neo4j PropertyGraphIndex, where it sets the "id" property of nodes to the same value as the "name" property, which can clash with other nodes. They are unsure why the "id" is set to a common string and are looking for a way around this issue. The community member also found a Cypher error in version 0.3.5 of the llama-index-graph-stores-neo4j package and had to revert to version 0.3.3. They couldn't find release notes for this package on PyPI and are wondering if they are available elsewhere.
In the comments, one community member suggests that the "id" is the "name" because there should only be one node for a given entity. Another community member points out that they can have sections across different documents with the same name, such as "Introduction" or "Appendix A", and wonders if the property graph is not intended for that type of ontology.
There is no explicitly marked answer in the post or comments.
Hello, I have a problem with neo4j PropertyGraphIndex, where it creates a contraint uniqueness for Entity and Node type nodes for the "id" property. But, it sets the id to the same value as name, which is common to other nodes and therefore clashes. Is there a way around this? Why is the id be set to a common string or at all? Or I'm missing something?
I also found that v0.3.5 has a cypher error. I had to revert to v0.3.3. This is on package llama-index-graph-stores-neo4j
Also, I didn't find release notes for this package on pip. Are they somewhere else? With you guys or neo4j people?
I can have sections across different documents with the same name: 1. Introduction, Appendix A, etc. Same for definitions, acronyms, etc. Or is the property graph not intended for that type of ontology?
