[
https://issues.apache.org/jira/browse/TAJO-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092406#comment-14092406
]
Hudson commented on TAJO-999:
-----------------------------
SUCCESS: Integrated in Tajo-master-build #329 (See
[https://builds.apache.org/job/Tajo-master-build/329/])
TAJO-999: SequenceFile key class need to be compatible. (jaehwa) (blrunner: rev
0603b49dddb5d2b3c6f6447fa672e0ea03eae09e)
* CHANGES
*
tajo-storage/src/test/java/org/apache/tajo/storage/TestCompressionStorages.java
*
tajo-storage/src/main/java/org/apache/tajo/storage/sequencefile/SequenceFileScanner.java
*
tajo-storage/src/main/java/org/apache/tajo/storage/sequencefile/SequenceFileAppender.java
* tajo-storage/src/test/java/org/apache/tajo/storage/TestStorages.java
> SequenceFile key class need to be compatible.
> ---------------------------------------------
>
> Key: TAJO-999
> URL: https://issues.apache.org/jira/browse/TAJO-999
> Project: Tajo
> Issue Type: Bug
> Components: storage
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.9.0
>
>
> Currently, tajo uses ByteWritable class for key class in SequenceFile. If we
> used ByteWritable class for key class, it is no problem. But if we use
> another class for key class, we must find IOException. For example, When I
> used LongWritable class for key class in TextSerde, I found error as follows:
> {code:xml}
> ERROR org.apache.tajo.worker.Task: wrong key class:
> org.apache.hadoop.io.BytesWritable is not class
> org.apache.hadoop.io.LongWritable
> java.io.IOException: wrong key class: org.apache.hadoop.io.BytesWritable is
> not class org.apache.hadoop.io.LongWritable
> at
> org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2251)
> at
> org.apache.tajo.storage.sequencefile.SequenceFileScanner.next(SequenceFileScanner.java:147)
> {code}
> Thus, we need to improve SequenceFileScanner and SequenceFileScannerAppender
> compatible for all writable classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
