oh,
its for for cassandra 1.x, right?
I use 2.0.7.
How could I reset leveled manifest in this case?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Tombstones-tp7594467p7594559.html
Sent from the cassandra-u...@incubator.apache.org mailing list
It's located beside SSTables and has a name in format .json
For `accounts` column family in `company` keyspace it looks like
/company/accounts/accounts.json
-Original Message-
From: Dimetrio [mailto:dimet...@flysoft.ru]
Sent: 18 мая 2014 г. 2:06
To: cassandra-u...@incubator.apache.org
Su
On 18 May 2014, at 10:30, Jan Algermissen wrote:
> Hi,
>
> in our project, we apparently have a problem or misunderstanding of the
> relationship between schema changes and data updates.
>
> One team is doing automated tests during build and deployment that executes
> data migration tests on
Colin,
On 18 May 2014, at 15:29, Colin wrote:
> Hi Jan,
>
> Try waiting a period of time, say 60 seconds, after modifying the schema so
> the changes propagate throughout the cluster.
>
> Also, you could add a step to your automation where you verify the schema
> change by attempting to inse
Hi Jan,
Try waiting a period of time, say 60 seconds, after modifying the schema so the
changes propagate throughout the cluster.
Also, you could add a step to your automation where you verify the schema
change by attempting to insert/delete from the schema with a higher consistency
level to m
Hi,
in our project, we apparently have a problem or misunderstanding of the
relationship between schema changes and data updates.
One team is doing automated tests during build and deployment that executes
data migration tests on a development cluster. In those migrations there will
be schema
