[
https://issues.apache.org/jira/browse/SOLR-18079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053303#comment-18053303
]
Jan Høydahl commented on SOLR-18079:
------------------------------------
I think if this json file is exposed to users, it is still a very hidden
expert-level option that fills a gap as a band-aid until a more holistic
solution is designed.
I totally agree that there should be more unified and pluggable ways to control
what gets loaded. We still have hardcoded lists in java classes for stuff that
should be SPI or other mechanisms. The proposal wrt implicit handlers and
possibly other components was basically:
{code:java}
<config>
<luceneMatchVersion>11.0</luceneMatchVersion>
<implicitHandlers query="true", update="true", admin="false"/>
<implicitResponseWriters/>
<implicitQueryParsers/>
</config>{code}
So whenever luceneMatchVersion < 11, Solr will auto add all the implicit stuff
as today. But from v11 on, you won't get anything that is not defined in
solrconfig.xml. I.e. you'll have to add whatever <implicitFoo bar="baz"/> tags
we add to the config in order to bring those endpoints in
> 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: 1h
> 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]
