Speaker: Theo Hultberg, Chief Architect at Burt
Video: http://www.youtube.com/watch?v=9vgKWPCztXw&list=PLqcm6qE9lgKLoYaakl3YwIWP4hmGsHm5e&index=13
I'm not a database driver expert, I'm just a Ruby developer who really likes Cassandra, but I've written a CQL driver. It wasn't hard, and it feels really good to now have an understanding of how my applications talk to Cassandra. To know what happens when I connect, prepare a statement, or how my data is encoded on its way to the database. When my CQL collections got big and I got weird results back, I could use my knowledge to quickly debug the issue. I'd like to give you an overview of the new native protocol from the driver perspective, maybe it can help you understand Cassandra the way it has helped me.
47. 01 00 03 09 00 00 00 2a 00 00 00 26
C T
*
F R O M
u s
H E R E
u s e r _ n a
?
81
7f
00
63
6e
00
1e
01
65
61
03
7a
00
00
6d
#CASSANDRAEU
08
82
00
05
65
00
d2
00
75
00
00
3c
01
73
0d
00
4e
00
65
3e
8a
0a
72
00
f3
6d
73
00
35
79
00
00
51
6b
09
04
71
65
75
S
e
m
E
r
e
L
E
W
=
00
a5
79
73
10
2f
73
65
ca
00
70
72
48
00
61
5f
@ICONARA
59. Map: a [short] n indicating the size of the map,
followed by n entries. Each entry is composed
of two [short bytes] representing the key and
the value of the entry map.
#CASSANDRAEU
@ICONARA