Viraj Bhat created HCATALOG-505:
-----------------------------------

             Summary: testSyntheticComplexSchema and testMapWithComplexData 
fail in JDK 1.7 64 bit
                 Key: HCATALOG-505
                 URL: https://issues.apache.org/jira/browse/HCATALOG-505
             Project: HCatalog
          Issue Type: Bug
          Components: test
    Affects Versions: 0.4, 0.5
         Environment: Java 1.7 64 bit and RHEL 6
            Reporter: Viraj Bhat
            Priority: Minor


Tests fail when doing the following:
{code}
private void verifyWriteRead 
{
   while (it.hasNext()) {
   Tuple input = data.get(i++);
   Tuple output = it.next();
   Assert.assertEquals(input.toString(), output.toString());
   LOG.info("tuple : {} ",output);
}
{code}

and is reported in the following way:
{quote}
Testcase: testSyntheticComplexSchema took 17.693 sec
        FAILED
expected:<...1#test 1,ac test2#test 2...> but was:<...2#test 2,ac test1#test 
1...>
junit.framework.ComparisonFailure: expected:<...1#test 1,ac test2#test 2...> 
but was:<...2#test 2,ac test1#test 1...>
        at 
org.apache.hcatalog.pig.TestHCatLoaderComplexSchema.verifyWriteRead(TestHCatLoaderComplexSchema.java:203)
        at 
org.apache.hcatalog.pig.TestHCatLoaderComplexSchema.testSyntheticComplexSchema(TestHCatLoaderComplexSchema.java:171)

Testcase: testTupleInBagInTupleInBag took 50.637 sec
Testcase: testMapWithComplexData took 12.558 sec
        FAILED
expected:<...2#(2,test 2),b test 1#(1,test 1...> but was:<...1#(1,test 1),b 
test 2#(2,test 2...>
junit.framework.ComparisonFailure: expected:<...2#(2,test 2),b test 1#(1,test 
1...> but was:<...1#(1,test 1),b test 2#(2,test 2...>
        at 
org.apache.hcatalog.pig.TestHCatLoaderComplexSchema.verifyWriteRead(TestHCatLoaderComplexSchema.java:203)
        at 
org.apache.hcatalog.pig.TestHCatLoaderComplexSchema.testMapWithComplexData(TestHCatLoaderComplexSchema.java:284)
{quote}

We may need to change the way we are comparing complex tuples!!

--
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