The community member is working with Neo4j property graphs and llamaindex, and has a specific use case where they need to insert documents dynamically at runtime. They also want to organize the data into different "tables" or "communities" in Neo4j, to store related entities and relationships in separate areas, such as a "marketing" place and an "academic/graduation" place.
The comments suggest that the community member can insert documents at runtime using index.insert(document) or index.insert_nodes(). However, the concept of separating data into different "communities" or "tables" is not entirely clear. Some community members suggest that in Neo4j, you can create different databases to achieve this, and provide a link to the Neo4j documentation on creating databases.
There is no explicitly marked answer, but the community members provide suggestions and guidance to help the original poster address their use case.
Organizing data into separate communities in neo4j with llamaindex
I'm working with Neo4j property graphs and using llamaindex, but I have a specific use case that I need help with. Most tutorials show how to load documents at load time, but I need to insert documents dynamically at runtime.
Also, I want to organize the data into different "tables" (I think they're called communities in Neo4j?), so I can store related entities and relationships in separate areas. For example, I want a "marketing" place, an "academic/graduation" place, and so on. Basically, different spaces for different types of graphs.
Hi, Logan. Yes, I think it will be fine. The only issue that is not quite clear for me is the concept of separating different kind of data in different kind of groups. In SQL we have tables, in graph stores idk yet. Maybe if I just place everything inside the same "place" as long as the entities and relationships don't collide I think I'll be fine, right? Since the documents doesn't share the same entities and relationships, they will be separated in the space I guess
