[
https://issues.apache.org/jira/browse/SOLR-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187183#comment-17187183
]
Erick Erickson commented on SOLR-13652:
---------------------------------------
Agreed. Either we need a copyField directive of everything to "text" or not
define df at all.
Doing a copyField is inelegant. Any "serious" installation will take it out.
Blah blah blah. It still allows you to get started without errors.
Pulling df out entirely will produce a pretty explicit error "no field name
specified in query and no default specified via 'df' param" for searches like
q=something if df isn't defined, but that;s not as helpful as getting results
back...
> Remove update from initParams in example solrconfig files that only mention
> "df"
> --------------------------------------------------------------------------------
>
> Key: SOLR-13652
> URL: https://issues.apache.org/jira/browse/SOLR-13652
> Project: Solr
> Issue Type: Improvement
> Components: examples
> Reporter: Erick Erickson
> Priority: Minor
> Labels: easyfix, newbie
>
> At least some of the solrconfig files we ship have this entry:
> <initParams
> path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse,update">
> <lst name="defaults">
> <str name="df">text</str>
> </lst>
> </initParams>
>
> which has lead at least one user to wonder if there's some kind of automatic
> way to have the df field populated for updates. I don't even know how you'd
> send an update that didn't have a specific field. We should remove the
> "update/**".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
