[ 
https://issues.apache.org/jira/browse/CASSANDRA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030368#comment-15030368
 ] 

Nirav Thakkar edited comment on CASSANDRA-10777 at 11/28/15 4:39 AM:
---------------------------------------------------------------------

Sorry, but we dont have AWS instance which can be used, But We noticed couple 
of difference in the file, if we use BIG-ENDian system as compared to 
LITTLE-ENDian system.  I am attaching the screenshots of the file- 
IndexSummary(LE and BE) which is used for the TestCase. There is small 
difference(BE vs LE) in the files if we create a keyspace and use "flush 
keyspace" to obtain the SSTable Files. 

The issue in the Test-case is while reading data as an integer, the value comes 
out to be very large, and we subtract 32 and check if its zero,and hence the 
assertion fails on BE system.


was (Author: nirav):
Sorry, but we dont have AWS instance which can be used, But We noticed couple 
of difference in the file, if we use BIG-ENDian system as compared to 
LITTLE-ENDian system.  I am attaching the screenshots of the files, one is the 
IndexSummary which is used for the TestCase. Similar difference is found if we 
create a keyspace and use "flush keyspace" to obtain the SSTable Files. 

The issue in the Test-case is while reading data as an integer, the value comes 
out to be very large, and we subtract 32 and check if its zero,and hence the 
assertion fails on BE system.

> LegacySSTableTest Test-case failure,  Issue with 
> test\data\legacy-sstables\jb\Keyspace1\Keyspace1-Standard1-jb-0-Summary.db  
> file read on BIG ENDian systems
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10777
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: OS:RHEL7 and BIG ENDian system
>            Reporter: Nirav Thakkar
>         Attachments: IndexSummaryBE.jpg, IndexSummaryLE.jpg
>
>
> I am building Cassandra 2.2.3 on BigEndian System. Cassandra builds 
> successfully. However there are quite a few test case failures. One of the 
> failing test case is LegacySSTableTest. This test case reads the file 
> test\data\legacy-sstables\jb\Keyspace1\Keyspace1-Standard1-jb-0-Summary.db
> Are these existing test data files, specific to Little Endian systems?
> I have observed differences in values read on a LE Vs BE systems.
> I use the following command to run the test case. ant test 
> -Dtest.name=LegacySSTableTest
> I get the following error:
> [junit] ------------- Standard Error -----------------
> [junit] Failed to read jb
> [junit] ------------- ---------------- ---------------
> [junit] Testcase: 
> testStreaming(org.apache.cassandra.io.sstable.LegacySSTableTest): FAILED
> [junit] null
> [junit] junit.framework.AssertionFailedError
> [junit] at 
> org.apache.cassandra.io.sstable.IndexSummary.<init>(IndexSummary.java:80)
> [junit] at 
> org.apache.cassandra.io.sstable.IndexSummary$IndexSummarySerializer.deserialize(IndexSummary.java:317)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.loadSummary(SSTableReader.java:877)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:730)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:692)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:480)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:376)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:371)
> [junit] at 
> org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:363)
> [junit] at 
> org.apache.cassandra.io.sstable.LegacySSTableTest.testStreaming(LegacySSTableTest.java:115)
> [junit] at 
> org.apache.cassandra.io.sstable.LegacySSTableTest.testStreaming(LegacySSTableTest.java:110)



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

Reply via email to