cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7241) Pig test fails on 2.1 branch
Date Tue, 27 May 2014 21:28:04 GMT


Brandon Williams commented on CASSANDRA-7241:

So, I took a different tack and ignored these errors, and instead focused on ThriftColumnFamilyDataTypeTest,
which fails with:

    [junit] Testcase: testCassandraStorageDataType(org.apache.cassandra.pig.ThriftColumnFamilyDataTypeTest):
   Caused an ERROR
    [junit] cannot be cast to
    [junit] java.lang.ClassCastException: cannot be cast
    [junit]     at org.apache.cassandra.pig.ThriftColumnFamilyDataTypeTest.testCassandraStorageDataType(

After a lengthy, tricky, painful bisect, I land back at CASSANDRA-5417.  This test fails 100%
of the time, and given the error I don't see how it can possibly be a timing issue.  So I
recreated this test using the cli and pig so I could run it manually, and I get this:

org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes deadbeef
        at org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(
        at org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(
        at org.apache.cassandra.db.marshal.AbstractType.compose(
        at org.apache.cassandra.hadoop.pig.AbstractCassandraStorage.columnToTuple(
        at org.apache.cassandra.hadoop.pig.CassandraStorage.getNext(
        at org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigRecordReader.nextKeyValue(
        at org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(
        at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(
        at org.apache.hadoop.mapred.MapTask.runNewMapper(
        at org.apache.hadoop.mapred.LocalJobRunner$

Which is interesting, since the deadbeef column is BytesType (verified in the cli), and the
line in ACS that throws is also from CASSANDRA-5417.

I'm left to conclude that, if the problem is in pig, it's still CASSANDRA-5417's fault :)
 I can attach the cli-ified script and very simple pig script to run against if needed.

> Pig test fails on 2.1 branch
> ----------------------------
>                 Key: CASSANDRA-7241
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alex Liu
>            Assignee: Brandon Williams
>             Fix For: 2.1 rc1
> run ant pig-test on cassandra-2.1 branch. There are many tests failed. I trace it a little
and find out Pig test fails starts from
> commit.
> It looks like storage changes break Pig tests.

This message was sent by Atlassian JIRA

View raw message