You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2010/04/11 09:10:41 UTC
[jira] Created: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Revert the io.serialization package to 0.20.2's api
---------------------------------------------------
Key: HADOOP-6698
URL: https://issues.apache.org/jira/browse/HADOOP-6698
Project: Hadoop Common
Issue Type: Bug
Components: io
Reporter: Owen O'Malley
Priority: Blocker
Fix For: 0.21.0
I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861982#action_12861982 ]
Doug Cutting commented on HADOOP-6698:
--------------------------------------
I should have been clearer: I'd vote to remove HADOOP-6420 as a part of this issue, since it's only current use case is to work with the serialization APIs that are being reverted in this issue.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861237#action_12861237 ]
Hadoop QA commented on HADOOP-6698:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442922/HADOOP-6698.patch
against trunk revision 938264.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 12 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/53/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/53/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/53/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/53/console
This message is automatically generated.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Patch Available (was: Open)
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Attachment: HADOOP-6698.patch
Here's a new patch which doesn't revert HADOOP-6420 (we can always revert if separately, if need be).
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860817#action_12860817 ]
Chris Douglas commented on HADOOP-6698:
---------------------------------------
bq. The patch I submitted backs out HADOOP-6420 - should I regenerate leaving it in?
Reverting it isn't part of this issue, but I'm +0 on retaining it. Is there another use case, other than the patch in MAPREDUCE-1126?
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860590#action_12860590 ]
Chris Douglas commented on HADOOP-6698:
---------------------------------------
bq. This issue is fundamentally about backing out changes related to HADOOP-1126, since you've rejected that patch. In that light, HADOOP-6420, HADOOP-6438 and HADOOP-6443 should perhaps also be backed out.
HADOOP-6420 was completed with MAPREDUCE-1126 as a use case, but it's an independent feature. Does it need to be backed out? Also, HADOOP-6438 was closed as invalid, not committed, so fortunately there's nothing to be backed out, there.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861977#action_12861977 ]
Doug Cutting commented on HADOOP-6698:
--------------------------------------
> HADOOP-6420 was completed with MAPREDUCE-1126 as a use case, but it's an independent feature. Does it need to be backed out?
If it has no other use cases, it should be backed out, no? If someone comes up with a use case, we can add it back, but, since it was added with MAPREDUCE-1126 as its only use case, and MAPREDUCE-1126 has stalled, I'd vote to back it out.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859601#action_12859601 ]
Hadoop QA commented on HADOOP-6698:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442493/HADOOP-6698.patch
against trunk revision 936463.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 2 new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/472/console
This message is automatically generated.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859998#action_12859998 ]
Hadoop QA commented on HADOOP-6698:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12442620/HADOOP-6698.patch
against trunk revision 936463.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/473/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/473/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/473/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/473/console
This message is automatically generated.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Open (was: Patch Available)
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860798#action_12860798 ]
Tom White commented on HADOOP-6698:
-----------------------------------
The patch I submitted backs out HADOOP-6420 - should I regenerate leaving it in?
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Attachment: HADOOP-6698.patch
Here's a patch which reverts all these changes.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861999#action_12861999 ]
Tom White commented on HADOOP-6698:
-----------------------------------
OK, I can remove HADOOP-6420 here. I'll commit this soon unless there are any objections.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Attachment: HADOOP-6698.patch
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Patch Available (was: Open)
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Resolution: Fixed
I've just committed this (https://issues.apache.org/jira/secure/attachment/12442620/HADOOP-6698.patch).
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Patch Available (was: Open)
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859432#action_12859432 ]
Tom White commented on HADOOP-6698:
-----------------------------------
We need to revert HADOOP-6165 to achieve this.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859562#action_12859562 ]
Tom White commented on HADOOP-6698:
-----------------------------------
Doug, I think you mean MAPREDUCE-1126 (not HADOOP-1126). Also HADOOP-6323 needs backing out.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated HADOOP-6698:
------------------------------
Status: Open (was: Patch Available)
Assignee: Tom White
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch, HADOOP-6698.patch
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6698) Revert the io.serialization package
to 0.20.2's api
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859555#action_12859555 ]
Doug Cutting commented on HADOOP-6698:
--------------------------------------
This issue is fundamentally about backing out changes related to HADOOP-1126, since you've rejected that patch. In that light, HADOOP-6420, HADOOP-6438 and HADOOP-6443 should perhaps also be backed out.
> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
> Key: HADOOP-6698
> URL: https://issues.apache.org/jira/browse/HADOOP-6698
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.