In CASSANDRA-1546, I propose an alternative to #1072. At it's core,
it rewrites #1072 without the clocks structure (by splitting the clock into
individual columns, not unlike what Zhu Han proposed in his preceding
mail, but in a row instead of a super column, for reason explained in the
issue).
It feels like 0.7.0-beta1 is becoming too distant a spec in the
rear-view, and the delta[1] is becoming quite large. I propose we
vote to release a new beta.
The previous vote was waved off, so here is a new one.
SVN: https://svn.apache.org/repos/asf/cassandra/tr...@r1001889
0.7.0-beta2
Function addColumn at class SuperColumn tries to atomically add a column to
the concurrent collection “columns_” using the following code:
Deletions in Cassandra involve an insertion of a tombstone rather than
actual column deletion.
In the case of this bit of code, I believe, and I am not
Glass half empty: we broke reading beta1 schemas. this is fixed in
https://issues.apache.org/jira/browse/CASSANDRA-1545 (which didn't
make it into this beta2 tag)
Glass half-full: starting to get used to taking 3 tries to approve a release :)
On Mon, Sep 27, 2010 at 1:48 PM, Eric Evans
On Mon, Sep 27, 2010 at 1:54 PM, Peter Schuller
peter.schul...@infidyne.com wrote:
In the case of this bit of code, I believe, and I am not speaking
authoritatively, the removal only happens in (1) the read path when
filtering results (on presumably query-local data) and (2) during
compaction
