...to avoid the supernode problem. The proposed fixes to the problem for Neo4j 1.6 won't really improve our use case, as most discussed solutions have involved partitioning a node's relationship space by direction and type, and the type hierarchy only uses outgoing '<>' edges.
Labels in Neo4j 2.0 should be the perfect solution for this. Holding off until then. Unfortunately, the change will be backward incompatible- I'll try to include a migration script as well.
...to avoid the supernode problem. The proposed fixes to the problem for Neo4j 1.6 won't really improve our use case, as most discussed solutions have involved partitioning a node's relationship space by direction and type, and the type hierarchy only uses outgoing '<>' edges.