Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Wed, 4 Dec 2013 15:06:35 +0000 (UTC)
From: "Chao Shi (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12682021.1385934241576.70286.1386169595838@arcas>
In-Reply-To: <JIRA.12682021.1385934241576@arcas>
References: <JIRA.12682021.1385934241576@arcas>
Subject: [jira] [Commented] (CRUNCH-308) Upgrade to Hadoop 2.2.0 and HBase
 0.96
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CRUNCH-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838962#comment-13838962 ] 

Chao Shi commented on CRUNCH-308:
---------------------------------

Great work, Josh!

I like the hack on PType. Just to make sure if I understand this correctly: no serialization will happen in our code when using KeyValue/Mutation with the output target directly (as this is handled by the MR framework). If we write them to a SeqFile target, it will call the ptype serialization function, i.e. HBaseTypes#MapOutFn. Am I right?

I think I will need to have closer look on this patch. :)

> Upgrade to Hadoop 2.2.0 and HBase 0.96
> --------------------------------------
>
>                 Key: CRUNCH-308
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-308
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Josh Wills
>         Attachments: CRUNCH-HBASE96.patch
>
>
> As discussed on dev@crunch, we should update Crunch to run against the new mainline releases of Hadoop (2.2.0) and HBase (0.96).
> There isn't a good way to maintain a shim between HBase 0.94 and HBase 0.96 due to a number of API changes, so this change means that support for HBase 0.94 will remain in the 0.8.x sequence of Crunch releases, and 0.96 will be the supported version from 0.9.0 onwards.


--
This message was sent by Atlassian JIRA
(v6.1#6144)