incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Nine <t...@spidertracks.com>
Subject Possible Bug in 0.8.2 with DynamicComposite range scans?
Date Wed, 10 Aug 2011 07:26:24 GMT
Hi guys,
  I've been dealing with a problem in my JPA plugin for a couple days
now.  I've been able to create a native test in 0.8.2 that reproduces
the issue.  Here is the test.


https://gist.github.com/3ce70eab8102d2555626


Essentially, here is what is happening.

A dynamic composite with the following ordering is created in a column

UTF8Type+BytesType(reversed=
true).

2 columns are then inserted, without composite encoding, these are the 2 values

"jeans" + 1293840000000L

"jeans" + 1294099200000L


Here are the byte values (with spaces added to make the encoding of
the composite easier to read)  The format is 4 byte comparator, 4 byte
length, n field bytes, 1 byte comparator, then repeats

Inserted:

8073 0005 6a65616e73 00    8042 0008 0000012d4b889b80 00
8073 0005 6a65616e73 00    8042 0008 0000012d3c158780 00

Query start

8073 0005 6a65616e73 00

Query end

8073 0005 6a65616e73 01

Returned from Hector Results

8073 0005 6a65616e73 00    8042 0008 0000012d3c158780 00
8073 0005 6a65616e73 00    8042 0008 0000012d4b889b80 00


Given that the first value is sorted normally, and the second value is
reversed, I would expect the higher long value to appear before the
lower one (the longs are dates) when the first value in the composite
is equal.  Is this the expected behavior, or is this a bug?

Thanks,
Todd

Mime
View raw message