Support for Fabric -

[neo-technology-build-agent]

Issue by graphadvantage Saturday Aug 08, 2020 at 14:56 GMT Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/1615

---

Guidelines

Feature description (Mandatory)

Apoc support for Neo4j Fabric operations, ability to directly merge virtual nodes and rels queried from Fabric shards. Ability to create a symmetric index for semantically identical nodes across shards, and use this index to merge vNodes for downstream query operations. Merged vNodes should retain metadata on their provenance (fabric graph id and node id) to support write back to the source shard. --> apoc.merge.vNodeFromFabricNode() , apoc.merge.vGraphFromFabricPaths()

Considered alternatives

Have some workarounds using existing apoc.create.vNode and apoc.create.vRelationship, nothing elegant :( https://community.neo4j.com/t/neo4j-fabric-sharded-subgraph-reassembly-for-advanced-querying/22731

How this feature can improve the project?

Ability to perform downstream operations/queries with elements drawn from fabric graph shards will improve the utility and adoption of fabric and enterprise graph sharding. Any real world implementation of fabric will necessarily involve hierarchy and other entities stored in multiple graph shards that will need virtual reassembly by the federated query to construct an accurate subgraph for downstream query operations. https://github.com/neo4j/neo4j/issues/12563

thank you!

Michael