hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GOEKE, MATTHEW (AG/1000)" <matthew.go...@monsanto.com>
Subject RE: mapreduce and python
Date Mon, 20 Jun 2011 21:55:27 GMT
You might want to chase down leads around https://issues.apache.org/jira/browse/MAPREDUCE-606.
It looks like there is a patch for it on Jira but I am not quite sure if it is working. If
it is worth it to you to keep it in python then it might be worth it to tinker with the patch...

HTH,
Matt

-----Original Message-----
From: Hassen Riahi [mailto:hassen.riahi@cern.ch] 
Sent: Monday, June 20, 2011 3:50 PM
To: mapreduce-user@hadoop.apache.org
Subject: Re: mapreduce and python

Thanks Matt for your reply...

I would like to use a binary file as input to a map code written in  
python.
All examples that I found take a text file as input to a map code (in  
python). Any ideas? is it feasible?

Hassen

> Hassen,
>
> If you would like to use python as input I would suggest looking  
> into the streaming api examples around Hadoop.
>
> Matt
>
> -----Original Message-----
> From: Hassen Riahi [mailto:hassen.riahi@cern.ch]
> Sent: Monday, June 20, 2011 3:13 PM
> To: mapreduce-user@hadoop.apache.org
> Subject: mapreduce and python
>
> Dear all,
>
> Is it possible to have a binary input to a map code written in python?
>
> Thank you
> Hassen
> This e-mail message may contain privileged and/or confidential  
> information, and is intended to be received only by persons entitled
> to receive such information. If you have received this e-mail in  
> error, please notify the sender immediately. Please delete it and
> all attachments from any servers, hard drives or any other media.  
> Other use of this e-mail by you is strictly prohibited.
>
> All e-mails and attachments sent and received are subject to  
> monitoring, reading and archival by Monsanto, including its
> subsidiaries. The recipient of this e-mail is solely responsible for  
> checking for the presence of "Viruses" or other "Malware".
> Monsanto, along with its subsidiaries, accepts no liability for any  
> damage caused by any such code transmitted by or accompanying
> this e-mail or any attachment.
>
>
> The information contained in this email may be subject to the export  
> control laws and regulations of the United States, potentially
> including but not limited to the Export Administration Regulations  
> (EAR) and sanctions regulations issued by the U.S. Department of
> Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient  
> of this information you are obligated to comply with all
> applicable U.S. export laws and regulations.
>


Mime
View raw message