You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jinho Kim (JIRA)" <ji...@apache.org> on 2014/09/26 04:10:33 UTC

[jira] [Resolved] (TAJO-1070) BSTIndexScanExec should not seek a negative offset

     [ https://issues.apache.org/jira/browse/TAJO-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinho Kim resolved TAJO-1070.
-----------------------------
    Resolution: Fixed

committed.
Thank you for the your review!

> BSTIndexScanExec should not seek a negative offset
> --------------------------------------------------
>
>                 Key: TAJO-1070
>                 URL: https://issues.apache.org/jira/browse/TAJO-1070
>             Project: Tajo
>          Issue Type: Task
>          Components: physical operator
>            Reporter: Jinho Kim
>            Assignee: Jinho Kim
>             Fix For: 0.9.0
>
>
> Recent hadoop filesystem apis defined strictly. So we should fix it correctly.
> https://issues.apache.org/jira/browse/HADOOP-9361
> It cause by unnecessary seek to -1
> {code}
> java.io.EOFException: Cannot seek to a negative offset
> 	at org.apache.hadoop.fs.FSInputChecker.seek(FSInputChecker.java:399)
> 	at org.apache.hadoop.fs.FSDataInputStream.seek(FSDataInputStream.java:62)
> 	at org.apache.hadoop.fs.ChecksumFileSystem$FSDataBoundedInputStream.seek(ChecksumFileSystem.java:325)
> 	at org.apache.tajo.storage.CSVFile$CSVScanner.seek(CSVFile.java:544)
> 	at org.apache.tajo.engine.planner.physical.BSTIndexScanExec.next(BSTIndexScanExec.java:119)
> 	at org.apache.tajo.engine.planner.physical.TestBSTIndexExec.testEqual(TestBSTIndexExec.java:184)
> {code}



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