[
https://issues.apache.org/jira/browse/SOLR-18095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059296#comment-18059296
]
ASF subversion and git services commented on SOLR-18095:
--------------------------------------------------------
Commit 746e8565833570a9146799682a03828874cc7c55 in solr's branch
refs/heads/branch_10x from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=746e8565833 ]
SOLR-18095: Add ability to map writer types and handlers to a No Operation
version. (#4091)
This approach for specifically response writers existed in previous versions of
Solr as a hidden feature/side effect of something else and was removed. It's
now restored for the specific purpose of disabling ImplicitPlugins created
components.
(cherry picked from commit e68d292f0506449707cc4a079c8f7d5da221d651)
> Allow users to remap writertypes and request handlers to No Operation verion
> ----------------------------------------------------------------------------
>
> Key: SOLR-18095
> URL: https://issues.apache.org/jira/browse/SOLR-18095
> Project: Solr
> Issue Type: Improvement
> Reporter: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In older versions of Solr there was a NoOpResponseWriter that could be used
> to disable a writer type. This was removed.
> This PR proposes to introduce a new NoOpResponseWriter and NoOpRequestHandler
> to let a user disable specific writer types and request handlers. The
> NoOpRequestHandler would return a 403 FORBIDDEN. The NoOpResponseWriter
> will either return a message in plain text or maybe return an exception?
>
> This would fit the existing pattern of folks customizing a core/collection
> level by modifying solrconfig.xml.
> This would be a minimal change to Solr, so could be backported as well.
>
> See SOLR-18079 for a related idea.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
