[
https://issues.apache.org/jira/browse/SOLR-18079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053540#comment-18053540
]
Eric Pugh commented on SOLR-18079:
----------------------------------
I think there are some things that obviously would be a mistake to remove. In
my specific use case the security folks have flagged concerns around CSV files.
While I can't go into the details, it's a "thing".
Since the deployment of Solr doesn't use CSV in any way, it seemed to make
sense to just remove the /update/csv request handler and the query response
writer type "csv". It alos just avoids the security folks tripping their
alarms.
The Solr is packaged up and deployed to a wide vareity of endusers, the team
doesn't directly deploy the Solr. But maybe they could ship a security.json?
However they would stil lhave to prove that CSV is not available..
An alternative is the PR I put up that lets you delete an API, but that is done
through the configset api.
> Allow users to provide their own ImplicitPlugins.json
> -----------------------------------------------------
>
> Key: SOLR-18079
> URL: https://issues.apache.org/jira/browse/SOLR-18079
> Project: Solr
> Issue Type: Improvement
> Components: config-api
> Reporter: Eric Pugh
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> If you want to control the plugins instantiated as part of setting up Solr,
> then you might want to have your own ImplicitPlugins.json
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
