[
https://issues.apache.org/jira/browse/SOLR-18537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138020#comment-18138020
]
Jason Gerlowski commented on SOLR-18537:
----------------------------------------
Hey this is awesome work all, what a quality of life improvement!
bq. It'd be nice to eventually remove the existing custom functionality in lieu
of this.
The one thing you may run into here is that the AdminHandlerProxy stuff has
support for sending requests to > 1 node, which I'm not sure
"X-Solr-targetNode" currently does? My hazy recollection is that this is
primarily used for things like making sure log-level updates in the Admin UI
are sent to all nodes.
> Proxy to any user-specified SolrCloud node by header/param
> ----------------------------------------------------------
>
> Key: SOLR-18537
> URL: https://issues.apache.org/jira/browse/SOLR-18537
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.2
>
> Attachments: response.md
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> It can be very useful for Solr to proxy requests to another node, specified
> in a header or param. The intended scenario is when there's an HTTP proxy in
> front of Solr, and the backing Solr nodes aren't directly reachable. Solr is
> doing that now for a few admin endpoints that have already been coded for it,
> using {{GenericV1RequestProxy}} internally (e.g. for logging, info, ...).
> The issue here instead proposes a generic mechanism that doesn't require Solr
> handlers to be coded any differently.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
