[
https://issues.apache.org/jira/browse/SOLR-17829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17829.
---------------------------------
Resolution: Won't Fix
> SolrJ: Introduce GenericCollectionRequest
> -----------------------------------------
>
> Key: SOLR-17829
> URL: https://issues.apache.org/jira/browse/SOLR-17829
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> There's a GenericSolrRequest that can be used to talk to Solr at either a
> node level or a Collection/Core specific request if setRequiresCollection is
> called. Here I propose clearly differentiating requests by being
> Collection/Core oriented or not according to the type. So we need a new
> GenericCollectionRequest, and setRequiresCollection becomes deprecated.
> I want to emphasize the collection-ness in the constructor, and make other
> aspects mandatory (e.g. request type).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
