[ https://issues.apache.org/jira/browse/SOLR-16847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776833#comment-17776833 ]
Jason Gerlowski commented on SOLR-16847: ---------------------------------------- Hi [~ahankinson] - I don't think this ticket is related to the behavior you're describing. The v2 API work (including this ticket) has so far steered pretty clear of the /select and /update endpoints. If I had to take a stab in the dark, I wonder whether SOLR-16916 is coming into play at all? Might be worth describing your behavior on the users list (us...@solr.apache.org) to see if anyone else has noticed similar - there are more eyes on that mailing list that might be able to help explain. > 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 > Assignee: Jason Gerlowski > Priority: Major > Labels: V2 > Fix For: main (10.0), 9.4 > > Time Spent: 1h 40m > 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: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org