[
https://issues.apache.org/jira/browse/SOLR-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145141#comment-14145141
]
Gregory Chanan commented on SOLR-6543:
--------------------------------------
[~noble.paul] thanks for pointing that out. Do you think it's still reasonable
to commit this? My "arbitrary filters" argument still applies, i.e. I may have
added my own filters that require PUT requests and for convenience and standard
error handling, I want to define my own Request/Response classes to handle
those requests via solrj the same as any other requests. Though I guess that
argues for supporting all HTTP methods, though PUT is probably the most common.
> Give HttpSolrServer the ability to send PUT requests
> ----------------------------------------------------
>
> Key: SOLR-6543
> URL: https://issues.apache.org/jira/browse/SOLR-6543
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: Gregory Chanan
> Priority: Minor
> Attachments: SOLR-6543.patch, SOLR-6543.patch
>
>
> Given that the schema API has a PUT request
> (https://cwiki.apache.org/confluence/display/solr/Schema+API#SchemaAPI-Createonenewschemafield)
> it would be nice if HttpSolrServer supported sending PUTs, so it could be
> used for sending that type of request. Note if we really wanted to fully
> support that request we'd probably want a Request/Response type in solrj as
> well, but that can be handled in a separate issue.
> Also, administrators may add arbitrary filters that require PUT requests. In
> my own setup, I have a version of Hadoop's
> DelegationTokenAuthenticationFilter sitting in front of the dispatch filter.
> Here also it would be nice if I could send all requests via HttpSolrServer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
