Hi Erick, I'll follow these guidelines. I'll open a IRA ticket for 3.6.1
Thank you Gautier On 12 Jul 2012, at 12:38, Erick Erickson wrote: > Gautier: > > It's perfectly appropriate to open a JIRA and attach your code as a > patch, thanks! > > If you haven't already seen it, this describes now to make patches, etc... > > http://wiki.apache.org/solr/HowToContribute > > Most IDEs have the ability to create them too, and "svn -diff" is easy > to do (execute that from the > dir that contains both solr and lucene for ease-of-use, please). > > We typically name patches as SOLR-####.patch, where ### is the JIRA number. > > Here's the JIRA link: https://issues.apache.org/jira/browse/solr, you > have to create > a user ID to add JIRAs/patches..... > > Code is always welcome! > > Best > Erick > > On Thu, Jul 12, 2012 at 6:43 AM, Gautier Koscielny <[email protected]> wrote: >> Hello, >> >> I work near Cambridge at the EMBL-EBI and I would like to contribute to >> SOLR. >> >> Our current project involved 2 teams developing a full text search service >> based on SOLR 3.6. >> >> We have had issues when trying to replicate a master copy of an index to a >> slave using HTTP proxy settings passed to the JRE. >> >> To solve this issue, I've created a copy of the SnapPuller and the >> ReplicationHandler, modified the code to manage >> proxy settings and modified the configuration of the SOLR slave to use this >> new handler. >> We have tested the replication using proxy settings in our environment with >> success. >> >> What I would like to do now is to apply these changes to the SnapPuller >> directly: >> - check proxy settings before creating the httpClient >> - apply the proxy setting to the httpClient HostConfiguration. >> >> I don't want to patch 3.6 and would like to apply the change to SOLR 4. >> >> Please, tell me what do you think about this change and if I can proceed. >> >> What is the usual procedure to commit code? >> >> Best regards, >> Gautier > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
