hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2094) hbase-2037 breaks mapreduce jobs going from 0.20.2 to 0.20.3
Date Wed, 06 Jan 2010 21:52:55 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797335#action_12797335

stack commented on HBASE-2094:

I ain't sure how to fix this.  The commons-lang addition is needed so Pair equals and hashcode
works; as is its broke.  We need the fat commons-lang because it knows how to create hash
codes for different types (Pair is generic so we need something that can work with its generaliity).
 It then knows how to do the equals properly handling arrays of objects if passed.  I looked
at pulling in pieces of commons-lang only but its hairball.  It looks like I'd end up pulling
in all of commons-lang (internally they refer to each other).

Either we pull hbase-2037 -- a working comparable Pair seems pivotal to hbase-2037 -- or we
expect that updating from 0.20.2 to 0.20.3, fellas need to update their MR CLASSPATHs.  I'm
leaning toward the former.

> hbase-2037 breaks mapreduce jobs going from 0.20.2 to 0.20.3
> ------------------------------------------------------------
>                 Key: HBASE-2094
>                 URL: https://issues.apache.org/jira/browse/HBASE-2094
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.20.3
> hbase-2037 makes it so commons-lang is now needed on mr classpath.  Can't have fellas
having to change their CLASSPATH on point release update.

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

View raw message