[
https://issues.apache.org/jira/browse/SOLR-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787141#comment-16787141
]
Gus Heck commented on SOLR-13306:
---------------------------------
A specific example of this is the de-normalization of two documents into a
single document using a join followed by an update expression. When the join
key has a 1-1 relationship with the routable section of the id used for
routing, then both parent and child documents are available localy, and
co-locating the denormalized form output by the update may be desirable as
well.
Also of interest would be any steps to avoid needless conversion to and
re-parsing from JSON (I'm still trying to determine if this is happening with
the patch I'm about to attach). In the specific case of an expression that ends
in an update it would be ideal if only the output from update listing the batch
sizes were serialized to JSON.
> Add a request parameter to execute a streaming expression locally
> -----------------------------------------------------------------
>
> Key: SOLR-13306
> URL: https://issues.apache.org/jira/browse/SOLR-13306
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: streaming expressions
> Affects Versions: 8.0
> Reporter: Gus Heck
> Assignee: Gus Heck
> Priority: Minor
>
> In some cases it is known (due to routing configuration) that all documents
> required for a streaming expression are co-located on the same server. In
> this case it is inefficient to send JSON over the wire, and it would be more
> efficient to issue the same expression to N servers, thereby saving transport
> and merge costs. Details, Patch and example to follow
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
