[
https://issues.apache.org/jira/browse/CASSANDRA-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000052#comment-14000052
]
Brandon Williams commented on CASSANDRA-7241:
---------------------------------------------
I get a lot of errors, but actually not that one. No configuration is required
for 'ant pig-test' so I'm not sure what happened there. I won't begin to
pretend this is the only problem we have with pig on 2.1. That said, what I am
concerned with here is:
{noformat}
[junit] Testcase:
testCqlStorageCompositeKeyTable(org.apache.cassandra.pig.CqlTableTest): FAILED
[junit] expected:<0> but was:<9>
[junit] junit.framework.AssertionFailedError: expected:<0> but was:<9>
[junit] at
org.apache.cassandra.pig.CqlTableTest.testCqlStorageCompositeKeyTable(CqlTableTest.java:167)
{noformat}
Which if you attempt to bisect from 2.0 to 2.1, lands you at CASSANDRA-5417,
but admittedly fails in even more tests there in different ways. Despite a
load of warnings, more things pass on current 2.1. Are there any other tickets
which might affect CASSANDRA-5417's behavior since then?
> Pig test fails on 2.1 branch
> ----------------------------
>
> Key: CASSANDRA-7241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7241
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alex Liu
> Assignee: Sylvain Lebresne
>
> 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
> https://github.com/apache/cassandra/commit/362cc05352ec67e707e0ac790732e96a15e63f6b
> commit.
> It looks like storage changes break Pig tests.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
