Hi William, The best approach is to submit patches. Chukwa has a bug tracking system which includes all development activities. See this page:
https://issues.apache.org/jira/browse/CHUKWA Patches are reviewed by the community to make sure it works and license compatible. Once a active individual contributor has been submitting patches for over a period of time, he/she is promoted to become a committer. A committer will have svn access to commit code. However, all changes still go through the same review process as before. Hope this helps. Regards, Eric On 8/3/10 2:26 PM, "William Bajzek" <williambaj...@gmail.com> wrote: > Hi Eric, > > I'm not sure how many people are really using MySQL in this capacity. I know > that one of the other people who has posted to the mailing list about i > recently is my coworker, so it's possible that our recent activity is giving > the impression of more demand than there really is. Our client is a big > corporation who plans to use Chukwa this way and I'm working on a patch for > them that does as you say. It is pretty small and straightforward. What would > be a good way to contribute it back to the community? > > > > On Jul 23, 2010, at 9:58 AM, Eric Yang wrote: >> >> MetricDataLoader can be modified to throw IOException to the executor class >> MetricDataLoaderPool, which can throw exception to PostProcessor Manager. >> PostProcessorManager moves the data to a temp directory. The retry logic >> can be added to PostProcessorManager by counting the number of retry with >> the error out sequence file before sending it to InError directory. It >> should be the better route to manages error conditions. >> >> It seems like a lot of people are using MySQL part of Chukwa. I am >> wondering what are the use cases? If we can have a driver on this part of >> the project, it could be better supported without fragment the community. > > > > - William Bajzek > williambaj...@gmail.com > > > > >
