[ 
https://issues.apache.org/jira/browse/HADOOP-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Klaas Bosteels updated HADOOP-1722:
-----------------------------------

    Attachment: HADOOP-1722-v4.patch

The failed contrib unit tests are not caused by the patch as far as I can tell, 
but I did find a small unrelated bug (serializing lists did not work properly 
in all cases). The 4th version of the patch contains a fix for this bug (as 
well as an update to the unit test that did not catch this bug before). 
Furthermore, I also changed the semantics of {{-typedbytes output}} once more. 
It now corresponds to

* {{stream.map.input.typed.bytes}}={{false}}
* {{stream.map.output.typed.bytes}}={{true}}
* {{stream.reduce.input.typed.bytes}}={{true}}
* {{stream.reduce.output.typed.bytes}}={{true}}

because it is more likely that you want to take text as input but use type 
bytes for everything else (instead of only using typed bytes for the reducer 
output).


> Make streaming to handle non-utf8 byte array
> --------------------------------------------
>
>                 Key: HADOOP-1722
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1722
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/streaming
>            Reporter: Runping Qi
>            Assignee: Klaas Bosteels
>         Attachments: HADOOP-1722-v2.patch, HADOOP-1722-v3.patch, 
> HADOOP-1722-v4.patch, HADOOP-1722.patch
>
>
> Right now, the streaming framework expects the output sof the steam process 
> (mapper or reducer) are line 
> oriented UTF-8 text. This limit makes it impossible to use those programs 
> whose outputs may be non-UTF-8
>  (international encoding, or maybe even binary data). Streaming can overcome 
> this limit by introducing a simple
> encoding protocol. For example, it can allow the mapper/reducer to hexencode 
> its keys/values, 
> the framework decodes them in the Java side.
> This way, as long as the mapper/reducer executables follow this encoding 
> protocol, 
> they can output arabitary bytearray and the streaming framework can handle 
> them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to