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

Ted Yu commented on HBASE-14380:
--------------------------------

This is reproducible:
{code}
testMROnTableWithCustomMapper(org.apache.hadoop.hbase.mapreduce.TestImportTsv)  
Time elapsed: 29.435 sec  <<< FAILURE!
java.lang.AssertionError: null
        at org.junit.Assert.fail(Assert.java:86)
        at org.junit.Assert.assertTrue(Assert.java:41)
        at org.junit.Assert.assertTrue(Assert.java:52)
        at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.validateTable(TestImportTsv.java:393)
        at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.doMROnTableTest(TestImportTsv.java:362)
        at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.doMROnTableTest(TestImportTsv.java:305)
        at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.testMROnTableWithCustomMapper(TestImportTsv.java:154)
{code}

> Correct data gets skipped along with bad data in importTsv bulk load thru 
> TsvImporterTextMapper
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-14380
>                 URL: https://issues.apache.org/jira/browse/HBASE-14380
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Bhupendra Kumar Jain
>            Assignee: Bhupendra Kumar Jain
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: 0001-HBASE-14380.patch, 14380-v2.txt, 
> HBASE-14380-branch-1.2.patch, HBASE-14380_v1.patch
>
>
> Cosider the input data is as below 
> ROWKEY, TIEMSTAMP, Col_Value
> r1,1,v1       >> Correct line
> r1             >> Bad line
> r1,3,v3       >> Correct line
> r1,4,v4       >> Correct line
> When data is bulk loaded using importTsv with mapper as TsvImporterTextMapper 
> ,  All the lines are getting ignored even though skipBadLines is set to true. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to