[
https://issues.apache.org/jira/browse/SOLR-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953934#comment-15953934
]
Joel Bernstein commented on SOLR-9337:
--------------------------------------
Another name for this could have been nestedLoopJoin. But for the functionality
I was looking to support at the time I didn't need to support all the different
join conditions (one-to-one, one-to-many, many-to-one, many-to-many etc...). So
rather then call it a join, I called it fetch. The full nestedLoopJoin
capability will be available in the future and it will be called by that name.
Eventually, possibly in Solr 7.0 fetch will be superseded by the nestedLoopJoin.
> Add fetch Streaming Expression
> ------------------------------
>
> Key: SOLR-9337
> URL: https://issues.apache.org/jira/browse/SOLR-9337
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Joel Bernstein
> Fix For: 6.3
>
> Attachments: SOLR-9337.patch, SOLR-9337.patch
>
>
> The fetch() Streaming Expression wraps another expression and fetches
> additional fields for documents in batches. The fetch() expression will
> stream out the Tuples after the data has been fetched. Fields can be fetched
> from any SolrCloud collection.
> Sample syntax:
> {code}
> daemon(
> update(collectionC, batchSize="100"
> fetch(collectionB,
> topic(checkpoints, collectionA, q="*:*", fl="a,b,c",
> rows="50"),
> fl="j,m,z",
> on="a=j")))
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
