You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Michel Tourn (JIRA)" <ji...@apache.org> on 2006/05/16 22:58:07 UTC

[jira] Reopened: (HADOOP-191) add hadoopStreaming to src/contrib

     [ http://issues.apache.org/jira/browse/HADOOP-191?page=all ]
     
Michel Tourn reopened HADOOP-191:
---------------------------------


An update to hadoop-streaming.



> add hadoopStreaming to src/contrib
> ----------------------------------
>
>          Key: HADOOP-191
>          URL: http://issues.apache.org/jira/browse/HADOOP-191
>      Project: Hadoop
>         Type: New Feature

>     Reporter: Michel Tourn
>     Assignee: Doug Cutting
>      Fix For: 0.2
>  Attachments: streaming.2.patch, streaming.3.patch, streaming.patch
>
> This is a patch that adds a src/contrib/hadoopStreaming directory to the source tree.
> hadoopStreaming is a bridge to run non-Java code as Map/Reduce tasks.
> The unit test TestStreaming runs the Unix tools tr (as Map) and uniq (as Reduce)
> TO test the patch: 
> Merge the patch. 
> The only existing file that is modified is trunk/build.xml
> trunk>ant deploy-contrib
> trunk>bin/hadoopStreaming : should show usage message
> trunk>ant test-contrib    : should run one test successfully
> TO add src/contrib/someOtherProject:
> edit src/contrib/build.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Please don't re-open closed bugs

Posted by Doug Cutting <cu...@apache.org>.
Please don't re-open closed bugs that are included in releases, since 
that messes up Jira's change log for the release.  Bugs normally 
transition from Open to Resolved/Fixed, then to Closed when a release is 
made.  It's okay to re-open a bug whose fix has not yet been released, 
but it is generally better to create a new bug in this case too.

Ideally I could modify the Jira permissions so that non-administrators 
cannot transition bugs from Closed to Open and are forced to instead 
start a new bug, but that does not appear to be possible.

Doug