--
Thanks for the good read Marko! In Bio Super Nodes Happen when you try to co-locate the Ontology in with the actual data (as opposed to saying type= as a property). Attributes that type things is usually bad for real queries... but I have always implemented that because of the super-node issue. Love the index idea, uberuseful!
Oh, and Dan's a good name ;)Dan
Sent from my iPhoneHello,Blueprints 2.x introduced the concept of vertex queries. I thought many of you might be interested in this post. It discusses the supernode problem and how it is overcome for property graphs. With specific focus on Titan and its vertex-centric indices.The results are pretty profound... a testament to this technique.Take care,Marko.--
--
--
--
this is the same solution we adopted in OrientDB about 10 months ago:
--
This is such great news!!
I've been waiting for this in Neo4j for way too long! (more than a year and a half...) and it's extremely important for the projects I'm developing such as Bio4j .Quick question, how hard would it be to move a DB from Neo4j to Titan?
--
If Bio4j is not written to TinkerPop, then there is solace in the fact that all graph software is premised on the same foundational concepts. There are vertices, edge, traversals, etc. Therefore, while there is code to be written, there are not new concepts to be learned.
--
If Bio4j is not written to TinkerPop, then there is solace in the fact that all graph software is premised on the same foundational concepts. There are vertices, edge, traversals, etc. Therefore, while there is code to be written, there are not new concepts to be learned.What about indexing? According to this discussion I found here: https://groups.google.com/forum/#!msg/neo4j/TWISaqitivo/vcbjZsxKDlAJ fulltext indexes are not directly available with Blueprints right?
Also, in the importing process I have to create many entities based on discoverability so I need to add/flush/query values in the same process. Would that be possible with Blueprints/Tinkerpop?
Full-text indexes are supported through Blueprints if the underlying storage layer (graph engine) supports full text search. Next, Titan will be supporting Elastic Search in the near future --- currently, there is no support for full text search in Titan.
Also, in the importing process I have to create many entities based on discoverability so I need to add/flush/query values in the same process. Would that be possible with Blueprints/Tinkerpop?I don't quite understand your question. Can you say more?
What I meant is that when I'm importing the data, I cannot do things like import all the nodes first and then connect them with all relationships that would be present in the database. On the contrary, I'm "discovering" nodes that I have to create and index on the way and I was concerned about the flushing of the indexed values I am doing all the time in the middle of the process. In the case where I couldn't add and flush an indexed value in the same transaction/process, that would be a problem because I would end up creating tones of redundant nodes and everything would just be a mess.
--Let me know if this is more understandable, otherwise I can try to explain it with an example of input data.Cheers,Pablo
Pablo Pareja TobesMy site http://about.me/pablopareja
--
--
--