-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TYPE_LONG: (Possible) Fix for Packing to 8bytes long (big endian) binary #48
Comments
Thanks this should be fixed for you in the latest commit - 55eed06. The toJSON/toArray method was flagging the keyspace wrapper in the wrong place, this looks like a bug which has been there for a while. Thanks for the pick up! -michael |
I applied the fix merging the diff,
prints:
But when loading, we have the key:
prints out:
Maybe something else in the toJSON method ? Thanks, |
Finally, if someone is using the previous releases of Pandra,
where two methods for pack and unpack binaries are stated in the current Pandra trunk commit. |
It seems that using CF with type long is not working at all.
I defined this CF:
}
Then I'm inserting new column this way:
Where two functions pack_longtype and unpack_longtype are from Cassandra FAQ:
http://wiki.apache.org/cassandra/FAQ#a_long_is_exactly_8_bytes
Pandra is responding:
So, I modified the function this way:
No insert were made in the CF, before that fix (multiline commented code).
After the fix, CF stats then were:
Column Family: RollupCheckpoint
SSTable count: 1
Space used (live): 381
Space used (total): 381
Memtable Columns Count: 3
Memtable Data Size: 99
Memtable Switch Count: 1
Read Count: 5
Read Latency: 0,059 ms.
Write Count: 6
Write Latency: 0,013 ms.
Pending Tasks: 0
Key cache capacity: 128
Key cache size: 0
Key cache hit rate: NaN
Row cache: disabled
Compacted row minimum size: 0
Compacted row maximum size: 0
Compacted row mean size: 0
So some insert were made in it !
The row converted to JSON was:
But when trying to read it:
I got
As you can see it lacks of NS and CF names, as required by the
but there's something inside of it.
So, what's happening with TYPE_LONG?
The text was updated successfully, but these errors were encountered: