[
https://issues.apache.org/jira/browse/SOLR-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208523#comment-15208523
]
Joel Bernstein commented on SOLR-8176:
--------------------------------------
I've been thinking about starting to work on this as well, but with a slightly
different approach then [~kwatters].
The approach I'm thinking of taking is fully distributed and doesn't rely on
low level query operations. Instead it moves the Iterative joins into a single
worker node that sees all the shards. That single worker node will issue
iterative joins using a batch nested loop approach. Cycle detection will be
implemented with a locally sorted list of visited nodes (on disk) that can be
intersected with the nodes coming back from the nested loop joins. This
approach will not be anywhere near as fast as the low level query work that
Kevin has done, but it will be really scalable and eventually always get to the
answer given enough time. So while the low level approach will be great for use
cases like access control, the fully distributed approach will be great for use
cases where the graph traversal is the main query and some allowances can be
made in the time it takes to complete.
> 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: [email protected]
For additional commands, e-mail: [email protected]
