[
https://issues.apache.org/jira/browse/SOLR-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208699#comment-15208699
]
Joel Bernstein edited comment on SOLR-8176 at 3/23/16 4:28 PM:
---------------------------------------------------------------
In regards to the tinkerpop discussions on this ticket. I think it makes sense
to first add some Streaming Expressions that model some basic graph traversal
use cases. This will iron out some of the mechanics involved in doing graph
traversals. This will start to build the foundation for supporting the Gremlin
query language. This was the same approach taken when the parallel relational
algebra expressions came first and became the foundation of the SQL interface.
This approach achieves a number of things:
1) It doesn't put the cart before the horse. In order to properly support
Gremlin we need a scalable distributed graph traversal capability. Once we have
that adding Gremlin or SparkQL support will be much easier then trying to
bootstrap graph capabilities while working on Gremlin at the same time.
2) We can then use Gremlin as a driver for building out the full range of graph
traversal streaming expressions. The SQL interface plays this role for the
parallel relational algebra Streaming Expressions.
3) Building out all Graph traversals as streaming expression means that we can
than directly plug in the graph expressions with the existing expression
library.
was (Author: joel.bernstein):
In regards to the tinkerpop discussions on this ticket. I think it makes sense
to first add some Streaming Expressions that model some basic graph traversal
use cases. This will iron out some of the mechanics involved in doing graph
traversals. This will start to build the foundation for supporting the Gremlin
query language. This was the same approach taken when the parallel relational
algebra came first and became the foundation of the SQL interface. This
approach achieves a number of things:
1) It doesn't put the cart before the horse. In order to properly support
Gremlin we need a scalable distributed graph traversal capability. Once we have
that adding Gremlin or SparkQL support will be much easier then trying to
bootstrap graph capabilities while working on Gremlin at the same time.
2) We can then use Gremlin as a driver for building out the full range of graph
traversal streaming expressions. The SQL interface plays this role for the
parallel relational algebra Streaming Expressions.
3) Building out all Graph traversals as streaming expression means that we can
than directly plug in the graph expressions with the existing expression
library.
> Model distributed graph traversals with Streaming Expressions
> -------------------------------------------------------------
>
> Key: SOLR-8176
> URL: https://issues.apache.org/jira/browse/SOLR-8176
> Project: Solr
> Issue Type: New Feature
> Components: clients - java, SolrCloud, SolrJ
> Affects Versions: master
> Reporter: Joel Bernstein
> Labels: Graph
> Fix For: master
>
>
> I think it would be useful to model a few *distributed graph traversal* use
> cases with Solr's *Streaming Expression* language. This ticket will explore
> different approaches with a goal of implementing two or three common graph
> traversal use cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
