Jack, yes re ownership. Mind opening an issue and reattaching? I saw this was done to 2 issues.
Thanks! Otis -- SOLR Performance Monitoring - http://sematext.com/spm On Dec 8, 2012 11:31 AM, "Jack Krupansky (JIRA)" <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527187#comment-13527187] > > Jack Krupansky commented on SOLR-4030: > -------------------------------------- > > bq. Now we fork > > Forking is understandable when you have time pressure and other interests > to satisfy. No problem there. Hopefully you can contribute back some of the > work from your fork. > > bq. taking our patches with us. > > How is that related to forking? I mean, sure, you can apply the patch on > your own fork, but why does forking imply that you think you need to delete > the posted patch? > > Besides, didn't you cede ownership of the patch to the community/ASF when > you posted it? So, technically, it is no longer yours, right? > > It sounds like you need a refresher course in "Community 101"! > > > > 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 > >