[jira] Commented: (MAPREDUCE-889) binary communication formats added to Streaming by HADOOP-1722 should be documented
[ https://issues.apache.org/jira/browse/MAPREDUCE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850284#action_12850284 ] Klaas Bosteels commented on MAPREDUCE-889: -- Obviously, the unit test failures are not related. binary communication formats added to Streaming by HADOOP-1722 should be documented --- Key: MAPREDUCE-889 URL: https://issues.apache.org/jira/browse/MAPREDUCE-889 Project: Hadoop Map/Reduce Issue Type: Bug Components: documentation Reporter: Amareshwari Sriramadasu Assignee: Klaas Bosteels Priority: Blocker Fix For: 0.21.0 Attachments: MAPREDUCE-889.patch, MAPREDUCE-889.patch binary communication formats added to Streaming by HADOOP-1722 should be documented in forrest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-889) binary communication formats added to Streaming by HADOOP-1722 should be documented
[ https://issues.apache.org/jira/browse/MAPREDUCE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaas Bosteels updated MAPREDUCE-889: - Status: Patch Available (was: Open) Looks like there are no more comments, so I'm going to send this through hudson... binary communication formats added to Streaming by HADOOP-1722 should be documented --- Key: MAPREDUCE-889 URL: https://issues.apache.org/jira/browse/MAPREDUCE-889 Project: Hadoop Map/Reduce Issue Type: Bug Components: documentation Reporter: Amareshwari Sriramadasu Assignee: Klaas Bosteels Priority: Blocker Fix For: 0.21.0 Attachments: MAPREDUCE-889.patch, MAPREDUCE-889.patch binary communication formats added to Streaming by HADOOP-1722 should be documented in forrest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-889) binary communication formats added to Streaming by HADOOP-1722 should be documented
[ https://issues.apache.org/jira/browse/MAPREDUCE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaas Bosteels updated MAPREDUCE-889: - Attachment: MAPREDUCE-889.patch Thanks Amareshwari, I've added the link. Any other comments? binary communication formats added to Streaming by HADOOP-1722 should be documented --- Key: MAPREDUCE-889 URL: https://issues.apache.org/jira/browse/MAPREDUCE-889 Project: Hadoop Map/Reduce Issue Type: Bug Components: documentation Reporter: Amareshwari Sriramadasu Assignee: Klaas Bosteels Priority: Blocker Fix For: 0.21.0 Attachments: MAPREDUCE-889.patch, MAPREDUCE-889.patch binary communication formats added to Streaming by HADOOP-1722 should be documented in forrest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-889) binary communication formats added to Streaming by HADOOP-1722 should be documented
[ https://issues.apache.org/jira/browse/MAPREDUCE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaas Bosteels updated MAPREDUCE-889: - Attachment: MAPREDUCE-889.patch Does the attached patch provide the documentation you had in mind, Amareshwari? binary communication formats added to Streaming by HADOOP-1722 should be documented --- Key: MAPREDUCE-889 URL: https://issues.apache.org/jira/browse/MAPREDUCE-889 Project: Hadoop Map/Reduce Issue Type: Bug Components: documentation Reporter: Amareshwari Sriramadasu Assignee: Klaas Bosteels Priority: Blocker Fix For: 0.21.0 Attachments: MAPREDUCE-889.patch binary communication formats added to Streaming by HADOOP-1722 should be documented in forrest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-889) binary communication formats added to Streaming by HADOOP-1722 should be documented
[ https://issues.apache.org/jira/browse/MAPREDUCE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaas Bosteels updated MAPREDUCE-889: - Assignee: Klaas Bosteels binary communication formats added to Streaming by HADOOP-1722 should be documented --- Key: MAPREDUCE-889 URL: https://issues.apache.org/jira/browse/MAPREDUCE-889 Project: Hadoop Map/Reduce Issue Type: Bug Components: documentation Reporter: Amareshwari Sriramadasu Assignee: Klaas Bosteels Priority: Blocker Fix For: 0.21.0 binary communication formats added to Streaming by HADOOP-1722 should be documented in forrest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-301) mapred.child.classpath.extension property
[
https://issues.apache.org/jira/browse/MAPREDUCE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-301:
-
Assignee: (was: Klaas Bosteels)
I have no need for this anymore, so I won't be implementing it myself any time
soon.
mapred.child.classpath.extension property
-
Key: MAPREDUCE-301
URL: https://issues.apache.org/jira/browse/MAPREDUCE-301
Project: Hadoop Map/Reduce
Issue Type: Improvement
Reporter: Klaas Bosteels
It would be useful to be able to extend the classpath for the task processes
on a job per job basis via a {{mapred.child.classpath.extension}} property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-764) TypedBytesInput's readRaw() does not preserve custom type codes
[
https://issues.apache.org/jira/browse/MAPREDUCE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-764:
-
Priority: Blocker (was: Major)
Making this a blocker since it should really go into 0.21.
TypedBytesInput's readRaw() does not preserve custom type codes
---
Key: MAPREDUCE-764
URL: https://issues.apache.org/jira/browse/MAPREDUCE-764
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Priority: Blocker
Attachments: MAPREDUCE-764.patch, MAPREDUCE-764.patch
The typed bytes format supports byte sequences of the form {{custom type
code length bytes}}. When reading such a sequence via
{{TypedBytesInput}}'s {{readRaw()}} method, however, the returned sequence
currently is {{0 length bytes}} (0 is the type code for a bytes array),
which leads to bugs such as the one described
[here|http://dumbo.assembla.com/spaces/dumbo/tickets/54].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-808) Buffer objects incorrectly serialized to typed bytes
[
https://issues.apache.org/jira/browse/MAPREDUCE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12738344#action_12738344
]
Klaas Bosteels commented on MAPREDUCE-808:
--
The failed tests seem to be ones that have been failing on Hudson for quite a
while now (and thus are not related to the patch).
Buffer objects incorrectly serialized to typed bytes
Key: MAPREDUCE-808
URL: https://issues.apache.org/jira/browse/MAPREDUCE-808
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Attachments: MAPREDUCE-808.patch
{{TypedBytesOutput.write()}} should do something like
{code}
Buffer buf = (Buffer) obj;
writeBytes(buf.get(), 0, bug.getCount());
{code}
instead of
{code}
writeBytes(((Buffer) obj).get());
{code}
since the bytes returned by {{Buffer.get()}} are only valid between 0 and
getCount() - 1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-808) Buffer objects incorrectly serialized to typed bytes
[
https://issues.apache.org/jira/browse/MAPREDUCE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-808:
-
Assignee: Klaas Bosteels
Status: Patch Available (was: Open)
Buffer objects incorrectly serialized to typed bytes
Key: MAPREDUCE-808
URL: https://issues.apache.org/jira/browse/MAPREDUCE-808
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Attachments: MAPREDUCE-808.patch
{{TypedBytesOutput.write()}} should do something like
{code}
Buffer buf = (Buffer) obj;
writeBytes(buf.get(), 0, bug.getCount());
{code}
instead of
{code}
writeBytes(((Buffer) obj).get());
{code}
since the bytes returned by {{Buffer.get()}} are only valid between 0 and
getCount() - 1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-764) TypedBytesInput's readRaw() does not preserve custom type codes
[
https://issues.apache.org/jira/browse/MAPREDUCE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-764:
-
Status: Patch Available (was: In Progress)
TypedBytesInput's readRaw() does not preserve custom type codes
---
Key: MAPREDUCE-764
URL: https://issues.apache.org/jira/browse/MAPREDUCE-764
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Attachments: MAPREDUCE-764.patch, MAPREDUCE-764.patch
The typed bytes format supports byte sequences of the form {{custom type
code length bytes}}. When reading such a sequence via
{{TypedBytesInput}}'s {{readRaw()}} method, however, the returned sequence
currently is {{0 length bytes}} (0 is the type code for a bytes array),
which leads to bugs such as the one described
[here|http://dumbo.assembla.com/spaces/dumbo/tickets/54].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-764) TypedBytesInput's readRaw() does not preserve custom type codes
[
https://issues.apache.org/jira/browse/MAPREDUCE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-764:
-
Status: In Progress (was: Patch Available)
TypedBytesInput's readRaw() does not preserve custom type codes
---
Key: MAPREDUCE-764
URL: https://issues.apache.org/jira/browse/MAPREDUCE-764
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Attachments: MAPREDUCE-764.patch, MAPREDUCE-764.patch
The typed bytes format supports byte sequences of the form {{custom type
code length bytes}}. When reading such a sequence via
{{TypedBytesInput}}'s {{readRaw()}} method, however, the returned sequence
currently is {{0 length bytes}} (0 is the type code for a bytes array),
which leads to bugs such as the one described
[here|http://dumbo.assembla.com/spaces/dumbo/tickets/54].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MAPREDUCE-764) TypedBytesInput's readRaw() does not preserve custom type codes
TypedBytesInput's readRaw() does not preserve custom type codes
---
Key: MAPREDUCE-764
URL: https://issues.apache.org/jira/browse/MAPREDUCE-764
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
The typed bytes format supports byte sequences of the form {{custom type code
length bytes}}. When reading such a sequence via {{TypedBytesInput}}'s
{{readRaw()}} method, however, the returned sequence currently is {{0 length
bytes}} (0 is the type code for a bytes array), which leads to bugs such as
the one described [here|http://dumbo.assembla.com/spaces/dumbo/tickets/54].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-764) TypedBytesInput's readRaw() does not preserve custom type codes
[
https://issues.apache.org/jira/browse/MAPREDUCE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaas Bosteels updated MAPREDUCE-764:
-
Status: Patch Available (was: Open)
TypedBytesInput's readRaw() does not preserve custom type codes
---
Key: MAPREDUCE-764
URL: https://issues.apache.org/jira/browse/MAPREDUCE-764
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: contrib/streaming
Affects Versions: 0.21.0
Reporter: Klaas Bosteels
Assignee: Klaas Bosteels
Attachments: MAPREDUCE-764.patch
The typed bytes format supports byte sequences of the form {{custom type
code length bytes}}. When reading such a sequence via
{{TypedBytesInput}}'s {{readRaw()}} method, however, the returned sequence
currently is {{0 length bytes}} (0 is the type code for a bytes array),
which leads to bugs such as the one described
[here|http://dumbo.assembla.com/spaces/dumbo/tickets/54].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
