[
https://issues.apache.org/jira/browse/SOLR-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462342#comment-13462342
]
Yonik Seeley commented on SOLR-3883:
------------------------------------
First guess is that it's probably safer/easier to add params we know we need
rather than remove params that could do things we don't want? It just seems
like that as we add new methods of creating documents in the future,
"dangerous" params could proliferate. Seems like it may be easier to enumerate
those params that are necessary/desirable for updates.
Brainstorming off the top of my head:
- Params for updates: commitWithin, NOW?
- Params for commits: softCommit, waitSearcher?
> distributed indexing forwards non-applicable request params
> -----------------------------------------------------------
>
> Key: SOLR-3883
> URL: https://issues.apache.org/jira/browse/SOLR-3883
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Yonik Seeley
> Priority: Blocker
> Fix For: 4.0
>
>
> Including all of the original request params can cause really undesirable
> stuff to happen.
> Reported by Dan Sutton:
> http://find.searchhub.org/document/c21c27f20e115ce9
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
