Steven Phillips created DRILL-211:
-------------------------------------

             Summary: index out of bounds exception when reading parquet file
                 Key: DRILL-211
                 URL: https://issues.apache.org/jira/browse/DRILL-211
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: M1
            Reporter: Steven Phillips


I see this when reading a table composed of 4 parquet files, each about 70MB.

java.lang.ArrayIndexOutOfBoundsException: 1048748
        parquet.bytes.BytesUtils.readIntLittleEndian(BytesUtils.java:54) 
~[parquet-common-1.0.1.jar:na]
        
org.apache.drill.exec.store.parquet.VarLenBinaryReader.readFields(VarLenBinaryReader.java:116)
 ~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
org.apache.drill.exec.store.parquet.ParquetRecordReader.next(ParquetRecordReader.java:387)
 ~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        org.apache.drill.exec.physical.impl.ScanBatch.next(ScanBatch.java:95) 
~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
org.apache.drill.exec.record.AbstractSingleRecordBatch.next(AbstractSingleRecordBatch.java:25)
 ~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
org.apache.drill.exec.physical.impl.sort.SortBatch.next(SortBatch.java:95) 
~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
org.apache.drill.exec.physical.impl.aggregate.AggBatch.next(AggBatch.java:68) 
~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
org.apache.drill.exec.physical.impl.ScreenCreator$ScreenRoot.next(ScreenCreator.java:77)
 ~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        org.apache.drill.exec.work.FragmentRunner.run(FragmentRunner.java:79) 
~[java-exec-1.0.0-m1-rebuffed.jar:1.0.0-m1]
        
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
[na:1.7.0_21]
        
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
[na:1.7.0_21]
        java.lang.Thread.run(Thread.java:722) [na:1.7.0_21]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to