[
https://issues.apache.org/jira/browse/SOLR-16847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750000#comment-17750000
]
ASF subversion and git services commented on SOLR-16847:
--------------------------------------------------------
Commit 9c43fc138b04c1420b912ec4371eea77335f905b in solr's branch
refs/heads/main from Alex Deparvu
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=9c43fc138b0 ]
SOLR-16847 Give v2 APIs access to solrconfig.xml config (#1778)
Prior to this commit, v2 APIs had no clean way to access any solrconfig.xml
configuration for their associated "requestHandler". This commit introduces
an interface, APIConfigProvider, which allows us to inject this configuration
to v2 API classes at call time in a "strongly-typed" way.
> Give v2 APIs access to solrconfig.xml config
> --------------------------------------------
>
> Key: SOLR-16847
> URL: https://issues.apache.org/jira/browse/SOLR-16847
> Project: Solr
> Issue Type: Improvement
> Components: v2 API
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: V2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Our v2 framework(s) still lack parity with our v1 RequestHandlers in one
> important area: configuration and initialization.
> v1 RequestHandlers have an {{init(NamedList)}} method which is called at
> creation time and allows RH's to handle any configuration attached to the
> relevant {{<requestHandler>}} tag in solrconfig.xml. This is most commonly
> used by administrators to override default values.
> We should add similar functionality to our JAX-RS framework. (It's also a
> gap in the homegrown annotation framework, but as we're moving away from this
> it's probably a much lower priority to add there).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
