[
https://issues.apache.org/jira/browse/SOLR-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892870#comment-16892870
]
Alexandre Rafalovitch commented on SOLR-13652:
----------------------------------------------
There is two reference to update there. One just update and one wildcard. The
proposal is to remove both?
I wonder if the wildcard option hits some sort of use-case that we may not
remember about.
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> 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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
