I just had an idéa. I'm currently working on "neo as a triple store" components and there are many cases when you have both the subject and the object (both nodes) and you would like to know which would be the most optimized node to start from when doing queries.
One simple measurement would be to count the relationships (and properties?) for both nodes and grab that which had the least, but that doesn't scale very well. What I want is either a Node#getRelationshipCount() or a Node#getEnergy() (which would be the amount of properties and relationships). Or it could be NeoService#getRelationshipCountForNode( long nodeId ) / NeoService#getNodeEnergy( long nodeId ). And the neo store would have knowledge of these counts/energies without actually counting them (one extra long per node in the store or something). At least I think it would be nice, and I'm sure others have though about it as well. / Mattias
_______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
