[
https://issues.apache.org/jira/browse/SOLR-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188989#comment-17188989
]
David Smiley commented on SOLR-13652:
-------------------------------------
SIP: Yes; maybe a simple one. I imagine you have the ideas/notions of what
the Solr getting started experience should be. [~marcussorealheis] would
likely collaborate with you on that vision. I'm unaware anyone _disagrees_
with a dedicated learning/getting-started configSet from something _else_
(default / minimal). I think there's different ideas on what the default one
should be; there was dev list discussion on that I recall recently, or maybe it
was a jira.
> 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
