[ https://issues.apache.org/jira/browse/SOLR-16847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776623#comment-17776623 ]
Andrew Hankinson edited comment on SOLR-16847 at 10/18/23 11:50 AM: -------------------------------------------------------------------- Is it possible that this change has changed the behaviour of default parameters in request handlers when using the JSON Query API? I have a list of default query fields (`qf`), but no default field (`df`) in my /select request handler. My application talks with Solr over the JSON Query API. Prior to upgrading to Solr 9.4.0, this worked fine. After updating I get an error: {code:java} Client exception => org.apache.solr.common.SolrException: no field name specified in query and no default specified via 'df' param{code} Queries in the Admin UI still work fine, but I believe this still uses the old GET-based request handler. Trying a simple JSON query in the "Documents" section of the admin UI produces this error for Solr 9.4, but works on Solr 9.3. was (Author: ahankinson): Is it possible that this change has changed the behaviour of default parameters when using the JSON Query API? I have a list of default query fields (`qf`), but no default field (`df`) in my /select request handler. My application talks with Solr over the JSON Query API. Prior to upgrading to Solr 9.4.0, this worked fine. After updating I get an error: {code:java} Client exception => org.apache.solr.common.SolrException: no field name specified in query and no default specified via 'df' param{code} Queries in the Admin UI still work fine, but I believe this still uses the old GET-based request handler. Trying a simple JSON query in the "Documents" section of the admin UI produces this error for Solr 9.4, but works on Solr 9.3. > 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