[
https://issues.apache.org/jira/browse/SOLR-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632578#comment-17632578
]
Jan Høydahl commented on SOLR-16504:
------------------------------------
I'm sure a GET request will do as well, I just chose the most light-weight one.
I'm also uncertain about our Http2SolrClient's support for auth. For
apache-http we had the static client-configurer that people could wire up in
solr.in.sh and SolrCLI would use it (basicAuth). I'm not aware of such for the
jetty client so maybe we need to open a ticket? I'm also pretty sure that
Hadoop Auth has some tight bindings to apache-http in the same lane.
Wrt internal internode communication with Auth, I'm our Auth classes have two
different superclass methods used to intercept auth, so I think we're covered?
There were some bugs early on that were plugged, but who knows what will
manifest when we convert all internal traffic?
> Convert CLI tools to Jetty HTTP 2 client.
> -----------------------------------------
>
> Key: SOLR-16504
> URL: https://issues.apache.org/jira/browse/SOLR-16504
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
> Labels: newdev
>
> Affected classes: SolrCLI, ExportTool, PackageTool, SolrLogPostTool
> The aforementioned classes are in the org.apache.solr.util package and are
> CLI tools (have a main method, are executed outside the context of a Solr
> server). These should be converted to our non-legacy Solr clients based on
> Jetty HttpClient. (i.e. don't use CloudLegacySolrClient or HttpSolrClient
> which are based on Apache HttpClient).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
