This is kind of  broad question, but I was playing with the graph streams and 
was having trouble making the tools work for what I wanted to do. I'm wondering 
if the use case for the graph streams really supports standard graph queries 
you might use with Gemlin or the like? I ask because right now we have two 
implementations of our data storage to support these two ways of looking at it, 
the standard query and the semantic filtering.

The usecases I usually see for the graph streams always seem to be limited to 
one link traversal for finding things related to nodes gathered from a query. 
But even with that it wasn't clear the best way to do things with lists of 
docvalues. So for example if you wanted to represent a node that had many doc 
values I had to use cross products to make a node for each doc value. The 
traversal didn't allow for that kind of node linking inherently it seemed.

So my question really is (and maybe this is not the place for this) what is the 
intent of these graph features and what is the goal for them in the future? I 
was really hoping at one point to only use solr for our product but it didn't 
seem feasible, at least not easily.

Thanks for all your help
Jonathan

Jonathan Nightingale
GXP Solutions Engineer
(office) 315 838 2273
(cell) 315 271 0688

Reply via email to