[
https://issues.apache.org/jira/browse/SOLR-17995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski resolved SOLR-17995.
------------------------------------
Fix Version/s: main(11.0)
10.1
Assignee: Jason Gerlowski
Resolution: Fixed
Marking this as closed - the relevant methods are deprecated in 10.1 and
removed altogether for 11.
> SolrStream API should separate baseUrl from core/collection
> -----------------------------------------------------------
>
> Key: SOLR-17995
> URL: https://issues.apache.org/jira/browse/SOLR-17995
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ, streaming expressions
> Reporter: David Smiley
> Assignee: Jason Gerlowski
> Priority: Major
> Labels: newdev, pull-request-available
> Fix For: main(11.0), 10.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{SolrStream}} takes a "baseUrl" but in practice, this is a URL that includes
> a core/collection. It even internally concatenates a "core" field (which
> cannot be set by user code) to baseUrl and then looks up a client with
> SolrClientCache. Ideally, these aspects would be well separated. A
> collection/core should be a required param, and it should be passed to the
> request method, which is overloaded to take it. This way the SolrClientCache
> isn't polluted with core/collection specific clients.
> Perhaps separate issue but it would be lovely to instantiate a SolrStream
> with an existing SolrClient, thus without bothering with SolrClientCache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
