As I mentioned last year I would like to start breaking up flume into separate repos. There are a few reasons for this: 1. Flume has grown so large that the CI system can no longer build it. The jobs run out of disk space due to the large logs. 2. The build takes a very long time to run. 3. There are several components that can no longer be practically be supported.
To this end I am planning on creating the following Git repos: flume-hadoop flume-http flume-irc flume-jdbc flume-jms flume-kafka flume-kudu flume-legacy flume-morphline flume-scribe flume-search flume-spring-boot flume-twitter For the time being I would propose everything else remain in the current Flume repo. Note that as each of these is populated they will each need to be released, However, most of these are fairly inactive so after the initial release they may not need to be touched very often. Also, since Jira now requires new users to request us to create accounts for them I would propose that as each of these repos are set up that they be configured to enable GitHub Issues. I am looking for feedback on this but if I don’t get any I plan to start work on this within a week or so. Ralph
