[
https://issues.apache.org/jira/browse/SOLR-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405645#comment-16405645
]
Joel Bernstein commented on SOLR-12122:
---------------------------------------
There are two issues to consider with adding multi-value hops.
1) Currently nodes are uniqued before any logic is applied. The unique
operation relies on the sort coming from the /export handler. Another technique
for uniquing nodes will need to be applied in the mult-value scenario.
2) We may not want to do an exhaustive pull of all the values from multi-valued
fields. We could consider using the significantTerms stream which works on
multi-valued fields already and limits the results based on a statistical
analysis.
The original code does a traditional breadth first traversal retrieving all
nodes in its path. Using significant terms would limit that walk to only
significant nodes.
> nodes expression should support multiValued walk target
> -------------------------------------------------------
>
> Key: SOLR-12122
> URL: https://issues.apache.org/jira/browse/SOLR-12122
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: streaming expressions
> Reporter: David Smiley
> Priority: Major
>
> The {{nodes}} streaming expression has a {{walk}} argument that articulates a
> pair of Solr fields of the form {{traversalFrom->traversalTo}}. It assumed
> that they are *not* multiValued. It _appears_ not difficult to add
> multiValued support to traversalTo; that's what this issue is about.
> See
> http://lucene.472066.n3.nabble.com/Using-multi-valued-field-in-solr-cloud-Graph-Traversal-Query-td4324379.html
> Note: {{gatherNodes}} appears to be the older name which is still supported.
> It's more commonly known as {{nodes}}. graph-traversal.adoc documents it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
