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

Aihua Xu commented on ACCUMULO-4672:
------------------------------------

HIVE-17373 is the jira that I'm trying to upgrade accumulo to 1.8.1. I just 
uploaded a new patch, but I tested this patch locally and noticed that we are 
hitting this NPE issue with the same stack trace. 

> NPE extracting samplerConfiguration from InputSplit
> ---------------------------------------------------
>
>                 Key: ACCUMULO-4672
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4672
>             Project: Accumulo
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 1.8.2, 2.0.0
>
>
> {noformat}
> Caused by: java.lang.NullPointerException
>       at 
> org.apache.accumulo.core.client.mapred.AbstractInputFormat$AbstractRecordReader.initialize(AbstractInputFormat.java:608)
>       at 
> org.apache.accumulo.core.client.mapred.AccumuloRowInputFormat$1.initialize(AccumuloRowInputFormat.java:60)
>       at 
> org.apache.accumulo.core.client.mapred.AccumuloRowInputFormat.getRecordReader(AccumuloRowInputFormat.java:84)
> {noformat}
> I still need to dig into this one and try to write a test case for it that 
> doesn't involve Hive (as it may have just been something that I was doing). 
> Best as I can tell..
> AbstractInputFormat extracts a default table configuration object from the 
> Job's Configuration class:
> {code}
>       InputTableConfig tableConfig = getInputTableConfig(job, 
> baseSplit.getTableName());
> {code}
> Eventually, the same class tries to extract the samplerConfiguration from 
> this tableConfig (after noticing it is not present in the InputSplit) and 
> this throws an NPE. Somehow the tableConfig was null. It very well could be 
> that Hive was to blame, I just wanted to make sure that this was captured 
> before I forgot about it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to