Thanks for the comments Cory! I've added subdirs-per-service support so a user can configure the hdfs subdirectory on the connecting flume charms (-syslog and -twitter). Config opt example:
http://bazaar.launchpad.net/~bigdata-dev/charms/trusty/apache-flume- twitter/trunk/view/head:/config.yaml#L19 Using the config in flume-hdfs: http://bazaar.launchpad.net/~bigdata-dev/charms/trusty/apache-flume- hdfs/trunk/view/head:/templates/flume.conf.j2#L25 I've also added a couple paragraphs at the bottom of the #Usage section to talk about where you can expect the data, and how to use -cat / -text once it gets there: http://bazaar.launchpad.net/~bigdata-dev/charms/trusty/apache-flume- hdfs/trunk/revision/15 Let me know what you think. -- You received this bug notification because you are a member of Juju Big Data Development, which is a bug assignee. https://bugs.launchpad.net/bugs/1478770 Title: New charm: apache-flume-hdfs Status in Juju Charms Collection: New Bug description: This charm provides a Flume agent designed to ingest events into the shared filesystem (HDFS) of a connected Hadoop cluster. It is meant to relate to other Flume agents such as apache-flume-syslog and apache- flume-twitter. Big Data charmers need to review the current state of this charm and verify its readiness for the charm store. To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+bug/1478770/+subscriptions -- Mailing list: https://launchpad.net/~bigdata-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~bigdata-dev More help : https://help.launchpad.net/ListHelp
