[jira] [Comment Edited] (CASSANDRA-15882) sstablemetadata should show tombstone timestamp not just the local drop time

2020-06-22 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142458#comment-17142458 ] Thanh edited comment on CASSANDRA-15882 at 6/22/20, 10:35 PM: --

[jira] [Commented] (CASSANDRA-15882) sstablemetadata should show tombstone timestamp not just the local drop time

2020-06-22 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142458#comment-17142458 ] Thanh commented on CASSANDRA-15882: ---   sorry, pls disregard this request, it's invalid.  I've

[jira] [Updated] (CASSANDRA-15882) sstablemetadata should show tombstone timestamp not just the local drop time

2020-06-22 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-15882: -- Resolution: Invalid Status: Resolved (was: Triage Needed) > sstablemetadata should show

[jira] [Updated] (CASSANDRA-15891) provide a configuration option such as endpoint_verification_method

2020-06-22 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-15891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-15891: -- Summary: provide a configuration option such as endpoint_verification_method (was: allow

[jira] [Created] (CASSANDRA-15891) allow cassandra admin to decide what endpoint to use for endpoint verification

2020-06-22 Thread Thanh (Jira)
Thanh created CASSANDRA-15891: - Summary: allow cassandra admin to decide what endpoint to use for endpoint verification Key: CASSANDRA-15891 URL: https://issues.apache.org/jira/browse/CASSANDRA-15891

[jira] [Updated] (CASSANDRA-15882) sstablemetadata should show tombstone timestamp not just the local drop time

2020-06-18 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-15882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-15882: -- Description: issue/request: sstablemetadata should show tombstone timestamp not just the local

[jira] [Created] (CASSANDRA-15882) sstablemetadata should show tombstone timestamp not just the local drop time

2020-06-18 Thread Thanh (Jira)
Thanh created CASSANDRA-15882: - Summary: sstablemetadata should show tombstone timestamp not just the local drop time Key: CASSANDRA-15882 URL: https://issues.apache.org/jira/browse/CASSANDRA-15882

[jira] [Comment Edited] (CASSANDRA-14200) NullPointerException when dumping sstable with null value for timestamp column

2020-05-15 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-14200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108654#comment-17108654 ] Thanh edited comment on CASSANDRA-14200 at 5/15/20, 9:26 PM: - You can

[jira] [Comment Edited] (CASSANDRA-14200) NullPointerException when dumping sstable with null value for timestamp column

2020-05-15 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-14200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108654#comment-17108654 ] Thanh edited comment on CASSANDRA-14200 at 5/15/20, 8:59 PM: - You can

[jira] [Commented] (CASSANDRA-14200) NullPointerException when dumping sstable with null value for timestamp column

2020-05-15 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-14200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108654#comment-17108654 ] Thanh commented on CASSANDRA-14200: --- You can workaround the problem by updating the bad "null"

[jira] [Commented] (CASSANDRA-14200) NullPointerException when dumping sstable with null value for timestamp column

2020-05-15 Thread Thanh (Jira)
[ https://issues.apache.org/jira/browse/CASSANDRA-14200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108649#comment-17108649 ] Thanh commented on CASSANDRA-14200: --- You can see the NPE by inserting data using JSON like this:

[jira] [Updated] (CASSANDRA-14184) Cleanup cannot run before a node has joined the ring

2018-01-22 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-14184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-14184: -- Description: Server log shows messages like [RMI TCP Connection(18)-127.0.0.1] 2018-01-20

[jira] [Created] (CASSANDRA-14184) Cleanup cannot run before a node has joined the ring

2018-01-22 Thread Thanh (JIRA)
Thanh created CASSANDRA-14184: - Summary: Cleanup cannot run before a node has joined the ring Key: CASSANDRA-14184 URL: https://issues.apache.org/jira/browse/CASSANDRA-14184 Project: Cassandra

[jira] [Created] (CASSANDRA-12208) Estimated droppable tombstones given by sstablemetadata counts tombstones that aren't actually "droppable"

2016-07-14 Thread Thanh (JIRA)
Thanh created CASSANDRA-12208: - Summary: Estimated droppable tombstones given by sstablemetadata counts tombstones that aren't actually "droppable" Key: CASSANDRA-12208 URL:

[jira] [Updated] (CASSANDRA-12204) sstable2json should let the user know that failure might have occurred due to lack of disk space

2016-07-14 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-12204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-12204: -- Description: $ sstable2json testks_0101-datatable-ka-61613-Data.db > ~/json61613

[jira] [Created] (CASSANDRA-12204) sstable2json should let the user know that failure might have occurred due to lack of disk space

2016-07-14 Thread Thanh (JIRA)
Thanh created CASSANDRA-12204: - Summary: sstable2json should let the user know that failure might have occurred due to lack of disk space Key: CASSANDRA-12204 URL:

[jira] [Updated] (CASSANDRA-12204) sstable2json should let the user know that failure might have occurred due to lack of disk space

2016-07-14 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-12204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanh updated CASSANDRA-12204: -- Description: $ sstable2json testks_0101-datatable-ka-61613-Data.db > ~/json61613

[jira] [Created] (CASSANDRA-11368) List of UDT can't be updated properly when using USING TIMESTAMP

2016-03-19 Thread Thanh (JIRA)
Thanh created CASSANDRA-11368: - Summary: List of UDT can't be updated properly when using USING TIMESTAMP Key: CASSANDRA-11368 URL: https://issues.apache.org/jira/browse/CASSANDRA-11368 Project:

[jira] [Created] (CASSANDRA-11356) EC2MRS ignores broadcast_rpc_address setting in cassandra.yaml

2016-03-15 Thread Thanh (JIRA)
Thanh created CASSANDRA-11356: - Summary: EC2MRS ignores broadcast_rpc_address setting in cassandra.yaml Key: CASSANDRA-11356 URL: https://issues.apache.org/jira/browse/CASSANDRA-11356 Project: Cassandra

[jira] [Commented] (CASSANDRA-6123) Break timestamp ties consistently for a given user requests

2015-01-05 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264808#comment-14264808 ] Thanh commented on CASSANDRA-6123: -- To be clear, this jira does _not_ apply to

[jira] [Commented] (CASSANDRA-8554) Node where gossip is disabled still shows as UP on that node; other nodes show it as DN

2015-01-02 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263305#comment-14263305 ] Thanh commented on CASSANDRA-8554: -- I asked Mark to change the title of this jira

[jira] [Commented] (CASSANDRA-8554) Node where gossip is disabled still shows as UP on that node; other nodes show it as DN

2015-01-02 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263309#comment-14263309 ] Thanh commented on CASSANDRA-8554: -- I meant to add in my initial comment: nodetool

[jira] [Commented] (CASSANDRA-8235) nodetool repair leaves behind empty snapshot directories

2014-11-03 Thread Thanh (JIRA)
[ https://issues.apache.org/jira/browse/CASSANDRA-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195465#comment-14195465 ] Thanh commented on CASSANDRA-8235: -- Hmm..It's working as expected for me, too. I

[jira] [Created] (CASSANDRA-8235) nodetool repair leaves behind empty snapshot directories

2014-10-31 Thread Thanh (JIRA)
Thanh created CASSANDRA-8235: Summary: nodetool repair leaves behind empty snapshot directories Key: CASSANDRA-8235 URL: https://issues.apache.org/jira/browse/CASSANDRA-8235 Project: Cassandra

[jira] [Created] (CASSANDRA-7903) tombstone created upon insert of new row

2014-09-08 Thread Thanh (JIRA)
Thanh created CASSANDRA-7903: Summary: tombstone created upon insert of new row Key: CASSANDRA-7903 URL: https://issues.apache.org/jira/browse/CASSANDRA-7903 Project: Cassandra Issue Type: Bug