[
https://issues.apache.org/jira/browse/HBASE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3111:
-------------------------
Attachment: 3111-2nd-attempt.txt
Problem looks to have been a little more insidious. TableInputFormat
implements Configurable. TableOutputFormat does not and hbase configs were
hoisted up into TOF inside in the RecordWriter constructor by calling
HBaseConfiguration.addHbaseResources(context); This doesn't looks like it
would ever pick up config. set by the job. Let me try this patch against
hudson. Committing it now. Here's a commit message.
{code}
M src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java
Changed mentions of 'quorum' to 'ensemble'.
M src/main/java/org/apache/hadoop/hbase/mapreduce/IdentityTableReducer.java
M src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormat.java
Minor formatting.
M src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormatBase.java
Removed unused imports and minor formatting.
M src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
Documented what the quorumAddress parameter is for.
Removed an unnecessary looking HBaseConfiguration.addHbaseResources(conf);
(and adjusted documentation of job to say no hbase config set by the
reduce setup method).
M src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java
Made this class implment Configurable. Moved creation of table from
RecordWrite constructor based off passed TaskAttemptContext instead
into the new setConf method. Added table and conf data members.
{code}
> TestTableMapReduce broken up on hudson
> --------------------------------------
>
> Key: HBASE-3111
> URL: https://issues.apache.org/jira/browse/HBASE-3111
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.90.0
>
> Attachments: 3111-2nd-attempt.txt
>
>
> So, test has failed for various reasons since fixed over last week or so. It
> is currently failing when the reducer starts up. Its failing because its not
> picking up the zk servers location; its using stale config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
