Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Constraints Instead of Plain Range Index for Node keys/ids #159

Open
zach-blumenfeld opened this issue Sep 29, 2024 · 0 comments
Open

Comments

@zach-blumenfeld
Copy link

Regarding stuff like this in kg writer: https://github.com/neo4j/neo4j-graphrag-python/blob/main/src/neo4j_graphrag/experimental/components/kg_writer.py#L103

For unique node ids/keys used in loading, you want to use a Constraint: Either Key or Uniqueness constraint. Key is like uniqueness but also doesn't allow Nulls and is Enterprise only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant