Also if they are general Hadoop big data examples were happy to carry them in bigtop as well ... Especially if they touch multiple areas of the Hadoop ecosystem
> On Jun 23, 2015, at 11:56 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > > Yea, throw them under dev-support. It'd be good to link them up on the wiki > or website too so they're more findable. > > Related, we could also use a README in dev-support as an overview of what > everything does. > >> On Tue, Jun 23, 2015 at 8:19 PM, Sean Busbey <bus...@cloudera.com> wrote: >> >> Could they go under dev-support? >> >>> On Tue, Jun 23, 2015 at 4:29 PM, Ray Chiang <rchi...@cloudera.com> wrote: >>> >>> So, as far as I can see, Hadoop has the main developer area for core >> Hadoop >>> code, unit tests in the test directories, user scripts (like >>> hadoop/mapred/yarn), and build scripts. >>> >>> I've got some utilities that are really for Hadoop contributors. These >>> serve two purposes: >>> >>> 1. These are just generally useful as private API examples >>> 2. They have some utility for developer purposes (e.g. the random >> .jhist >>> generator I'm working on for MAPREDUCE-6376) >>> >>> Does anyone have suggestions for where such code bits (and possibly >>> corresponding scripts) should go? >>> >>> -Ray >> >> >> >> -- >> Sean >>
