Cassandra Persister

[anfabiandrei]

No description provided.

[thorwhalen]

KEYS_TABLE and VALUES_TABLE are hardcoded. It should be controllable from init (though of course, it can have defaults.

Can you explain what your implementation of key:value store actually does and why it does it this way?

If I had to guess: It seems to me that you have two tables: One for keys, one for values, and that (key, value) pairs are created through a key_id that they share. The reason (again, a guess) it does this is because cassandra doesn't have the flexibility of indexing that say, mongo has, so you manage to get complex keys (and values) by using tables, and joining them.

What happens if you write to a same key twice? It seems key unicity won't be enforced (as in, say, files, where you can only have one content under one file-path. By what means can we enforce unicity in cassandra?