On Thu, Jun 20, 2019 at 7:37 AM Alexander Dejanovski
wrote:
> Hi Leo,
>
> The overlapping SSTables are indeed the most probable cause as suggested
> by Jeff.
> Do you know if the tombstone compactions actually triggered? (did the
> SSTables name change?)
>
Hello !
I believe they have changed. I
To cassandra's pioneers:
Dear cassandra's pioneer, is there a fast import data tool from oracle to
cassandra besides java-coding? I used copy from command to import oracle's date
to cassandra's timestamp, but cassandra's timestamp validating is too strict to
permit a no second part time, such
Hi Leo,
The overlapping SSTables are indeed the most probable cause as suggested by
Jeff.
Do you know if the tombstone compactions actually triggered? (did the
SSTables name change?)
Could you run the following command to list SSTables and provide us the
output? It will display both their timesta
Probably overlapping sstables
Which compaction strategy?
> On Jun 19, 2019, at 9:51 PM, Léo FERLIN SUTTON
> wrote:
>
> I have used the following command to check if I had droppable tombstones :
> `/usr/bin/sstablemetadata --gc_grace_seconds 259200
> /var/lib/cassandra/data/stats/tablename/md
I have used the following command to check if I had droppable tombstones :
`/usr/bin/sstablemetadata --gc_grace_seconds 259200
/var/lib/cassandra/data/stats/tablename/md-sstablename-big-Data.db`
I checked every sstable in a loop and had 4 sstables with droppable
tombstones :
```
Estimated droppab
Hi Again,
Trying to push this up as I wasn't able to find the root cause of this
issue.
Perhaps I need to upgrade to 3.0 first?
Will be happy to get some ideas.
Opened https://issues.apache.org/jira/browse/CASSANDRA-15172 with more
details.
Thanks!
On Thu, Jun 6, 2019 at 5:31 AM Jonathan Koppen
Thanks Michael and Sean. That was very useful.
Regards
Anurag
On Mon, Jun 17, 2019 at 7:07 PM Durity, Sean R
wrote:
> The advice so far is exactly correct for an in-place kind of upgrade. The
> blog post you mentioned is different. They decided to jump versions in
> Cassandra by standing up a n
Hi everyone,
I'm struggling to understand how can I query TTL on the row in collection (
Cassandra 3.11.4 ).
Here is my schema:
CREATE TYPE item (
csn bigint,
name text
);
CREATE TABLE products (
product_id bigint PRIMARY KEY,
items map>
);
And I'm creating records with TTL like this:
