[
https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527232#comment-13527232
]
Jack Krupansky commented on SOLR-4030:
--------------------------------------
bq. if a contributor wishes to withdraw his own work - especially if it's not
yet committed to the codebase - we should simply allow them to do so.
That makes sense at least for a short interval, except for the case of anyone
who may have included the patch in their own fork and maybe even could be in
production with it and is now in limbo or worse. In this specific instance the
triviality and brief tenure of the patch kind of makes it moot, but for future
instances now we have to think twice when recommending a non-committed patch.
At a minimum, somewhere there needs to be a notice/warning that use and
ownership of uncommitted patches is a potentially questionable and risky
activity - and that permisssion can be revoked at any moment. And if the
"donate" check box can't be restored, then there needs to be some mechanism for
a donor to explicitly cede ownership, to at least confirm the donation even if
its legal status may vary from jurisdiction to jurisdiction.
> Use Lucene segment merge throttling
> -----------------------------------
>
> Key: SOLR-4030
> URL: https://issues.apache.org/jira/browse/SOLR-4030
> Project: Solr
> Issue Type: Improvement
> Reporter: Radim Kolar
> Priority: Minor
> Labels: patch
> Fix For: 4.1, 5.0
>
>
> add argument "maxMergeWriteMBPerSec" to Solr directory factories.
--
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
