[jira] [Updated] (CASSANDRA-14908) Deadlock occurs when executing a file selection in levelcompact

[ https://issues.apache.org/jira/browse/CASSANDRA-14908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu taiyin updated CASSANDRA-14908: -- Attachment: (was: deadlock stack.txt) > Deadlock occurs when executing a file

[jira] [Commented] (CASSANDRA-14908) Deadlock occurs when executing a file selection in levelcompact

[ https://issues.apache.org/jira/browse/CASSANDRA-14908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702600#comment-16702600 ] wu taiyin commented on CASSANDRA-14908: --- Thank you very much for you reply first. Yes, The

[jira] [Commented] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

[ https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702747#comment-16702747 ] mck commented on CASSANDRA-14823: - [~bdeggleston], correct me if i'm wrong please… For this to

[jira] [Created] (CASSANDRA-14915) Handle ant-optional dependency

Marcus Eriksson created CASSANDRA-14915: --- Summary: Handle ant-optional dependency Key: CASSANDRA-14915 URL: https://issues.apache.org/jira/browse/CASSANDRA-14915 Project: Cassandra

[jira] [Commented] (CASSANDRA-14915) Handle ant-optional dependency

[ https://issues.apache.org/jira/browse/CASSANDRA-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702815#comment-16702815 ] Marcus Eriksson commented on CASSANDRA-14915: - tested on Debian, Linux Mint and Fedora

[jira] [Comment Edited] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

[ https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702747#comment-16702747 ] mck edited comment on CASSANDRA-14823 at 11/29/18 5:54 AM: ---

[jira] [Comment Edited] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

[ https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702747#comment-16702747 ] mck edited comment on CASSANDRA-14823 at 11/29/18 6:01 AM: ---

[jira] [Updated] (CASSANDRA-14908) Deadlock occurs when executing a file selection in levelcompact

[ https://issues.apache.org/jira/browse/CASSANDRA-14908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wu taiyin updated CASSANDRA-14908: -- Attachment: stack.zip > Deadlock occurs when executing a file selection in levelcompact >

[jira] [Comment Edited] (CASSANDRA-14823) Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

[ https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702747#comment-16702747 ] mck edited comment on CASSANDRA-14823 at 11/29/18 6:00 AM: ---

[jira] [Commented] (CASSANDRA-4592) CQL COPY TO command doesn't work with python cassandra-dbapi2

[ https://issues.apache.org/jira/browse/CASSANDRA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701804#comment-16701804 ] Jatin commented on CASSANDRA-4592: -- [~brandon.williams] , [~tpatterson] I have imported cqlsh

[jira] [Updated] (CASSANDRA-14914) Deserialization Error

[ https://issues.apache.org/jira/browse/CASSANDRA-14914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EDSON VICENTE CARLI JUNIOR updated CASSANDRA-14914: --- Description:   I have a single cassandra, now this

[jira] [Updated] (CASSANDRA-14894) RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

[ https://issues.apache.org/jira/browse/CASSANDRA-14894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14894: Status: Ready to Commit (was: Patch Available) > RangeTombstoneList doesn't

[jira] [Updated] (CASSANDRA-14914) Deserialization Error

[ https://issues.apache.org/jira/browse/CASSANDRA-14914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. Scott Andreas updated CASSANDRA-14914: - Component/s: Core > Deserialization Error > - > >

[6/6] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3834a270 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3834a270 Diff:

[2/6] cassandra git commit: Reading legacy tables handles tombstones for dropped collections

Reading legacy tables handles tombstones for dropped collections Patch by Sam Tunnicliffe; reviewed by Aleksey Yeschenko and Benedict Elliott Smith for CASSANDRA-14912 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Updated] (CASSANDRA-14912) LegacyLayout errors on collection tombstones from dropped columns

[ https://issues.apache.org/jira/browse/CASSANDRA-14912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14912: Fix Version/s: (was: 3.11.x) (was: 3.0.x)

[5/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/64d828b9 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/64d828b9 Diff:

[1/6] cassandra git commit: Reading legacy tables handles tombstones for dropped collections

Repository: cassandra Updated Branches: refs/heads/cassandra-3.0 c9dc69dce -> 0a7fbee43 refs/heads/cassandra-3.11 54be1fa8f -> 64d828b9d refs/heads/trunk cdeac4992 -> 3834a270f Reading legacy tables handles tombstones for dropped collections Patch by Sam Tunnicliffe; reviewed by Aleksey

[3/6] cassandra git commit: Reading legacy tables handles tombstones for dropped collections

Reading legacy tables handles tombstones for dropped collections Patch by Sam Tunnicliffe; reviewed by Aleksey Yeschenko and Benedict Elliott Smith for CASSANDRA-14912 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Updated] (CASSANDRA-14912) LegacyLayout errors on collection tombstones from dropped columns

[ https://issues.apache.org/jira/browse/CASSANDRA-14912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14912: Resolution: Fixed Status: Resolved (was: Ready to Commit) Thanks,

[4/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/64d828b9 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/64d828b9 Diff:

[jira] [Updated] (CASSANDRA-14914) Deserialization Error

[ https://issues.apache.org/jira/browse/CASSANDRA-14914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EDSON VICENTE CARLI JUNIOR updated CASSANDRA-14914: --- Attachment: mutation4465429258841992355dat >

[jira] [Commented] (CASSANDRA-14912) LegacyLayout errors on collection tombstones from dropped columns

[ https://issues.apache.org/jira/browse/CASSANDRA-14912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701897#comment-16701897 ] Sam Tunnicliffe commented on CASSANDRA-14912: - Adding the first {{isComplex}} check (as

[jira] [Commented] (CASSANDRA-14894) RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

[ https://issues.apache.org/jira/browse/CASSANDRA-14894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701965#comment-16701965 ] Sam Tunnicliffe commented on CASSANDRA-14894: - +1 > RangeTombstoneList doesn't properly

[jira] [Created] (CASSANDRA-14914) Deserialization Error

EDSON VICENTE CARLI JUNIOR created CASSANDRA-14914: -- Summary: Deserialization Error Key: CASSANDRA-14914 URL: https://issues.apache.org/jira/browse/CASSANDRA-14914 Project: Cassandra

[jira] [Commented] (CASSANDRA-12700) During writing data into Cassandra 3.7.0 using Python driver 3.7 sometimes Connection get lost, because of Server NullPointerException

[ https://issues.apache.org/jira/browse/CASSANDRA-12700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701825#comment-16701825 ] Alexander Pugachev commented on CASSANDRA-12700: [~rajesh_con] How did you apply the

[jira] [Commented] (CASSANDRA-14912) LegacyLayout errors on collection tombstones from dropped columns

[ https://issues.apache.org/jira/browse/CASSANDRA-14912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701910#comment-16701910 ] Benedict commented on CASSANDRA-14912: -- +1 > LegacyLayout errors on collection tombstones from

[1/6] cassandra git commit: RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

Repository: cassandra Updated Branches: refs/heads/cassandra-3.0 0a7fbee43 -> f7630e4c3 refs/heads/cassandra-3.11 64d828b9d -> 4a531c27c refs/heads/trunk 3834a270f -> f2520d7a5 RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases Patch by Blake

[2/6] cassandra git commit: RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases Patch by Blake Eggleston; Reviewed by Sam Tinnicliffe for CASSANDRA-14894 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[3/6] cassandra git commit: RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases Patch by Blake Eggleston; Reviewed by Sam Tinnicliffe for CASSANDRA-14894 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[5/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4a531c27 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4a531c27 Diff:

[4/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4a531c27 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4a531c27 Diff:

[6/6] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f2520d7a Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f2520d7a Diff:

[jira] [Commented] (CASSANDRA-9167) Improve bloom-filter false-positive-ratio

[ https://issues.apache.org/jira/browse/CASSANDRA-9167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702276#comment-16702276 ] Ariel Weisberg commented on CASSANDRA-9167: --- I don't want to derail this, but the way most

[jira] [Commented] (CASSANDRA-14848) When upgrading 3.11.3->4.0 using SSL 4.0 nodes does not connect to old non seed nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702232#comment-16702232 ] Ariel Weisberg commented on CASSANDRA-14848: [~tommy_s] there is an issue with 4.0 nodes

[jira] [Commented] (CASSANDRA-14911) Misc docs grammar, spelling and capitalization issues

[ https://issues.apache.org/jira/browse/CASSANDRA-14911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702409#comment-16702409 ] Ariel Weisberg commented on CASSANDRA-14911: Thanks [~laran]. I need to check if this

[jira] [Commented] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702416#comment-16702416 ] Ariel Weisberg commented on CASSANDRA-11939: Hey when you update patches can you delete

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns are consistent for proxyhistograms and cfhistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Summary: Make Read and Write Latency columns are consistent for proxyhistograms

[jira] [Comment Edited] (CASSANDRA-11939) Read and Write Latency columns are swapped in proxyhistograms vs cfhistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702416#comment-16702416 ] Ariel Weisberg edited comment on CASSANDRA-11939 at 11/28/18 9:58 PM:

[jira] [Updated] (CASSANDRA-14894) RangeTombstoneList doesn't properly clean up mergeable or superseded rts in some cases

[ https://issues.apache.org/jira/browse/CASSANDRA-14894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-14894: Resolution: Fixed Status: Resolved (was: Ready to Commit) thanks,

[jira] [Commented] (CASSANDRA-14908) Deadlock occurs when executing a file selection in levelcompact

[ https://issues.apache.org/jira/browse/CASSANDRA-14908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702330#comment-16702330 ] Ariel Weisberg commented on CASSANDRA-14908: This doesn't look like a deadlock as

[jira] [Commented] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702323#comment-16702323 ] Ariel Weisberg commented on CASSANDRA-14896: 4.0 is providing the wrong max version when

[jira] [Assigned] (CASSANDRA-14911) Misc docs grammar, spelling and capitalization issues

[ https://issues.apache.org/jira/browse/CASSANDRA-14911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg reassigned CASSANDRA-14911: -- Assignee: Laran Evans > Misc docs grammar, spelling and capitalization

[jira] [Updated] (CASSANDRA-14911) Misc docs grammar, spelling and capitalization issues

[ https://issues.apache.org/jira/browse/CASSANDRA-14911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-14911: --- Reviewers: Ariel Weisberg Reviewer: Ariel Weisberg > Misc docs grammar,

[jira] [Commented] (CASSANDRA-11939) Make Read and Write Latency columns are consistent for proxyhistograms and cfhistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702433#comment-16702433 ] Ariel Weisberg commented on CASSANDRA-11939: [Trunk

[jira] [Commented] (CASSANDRA-11323) When node runs out of commitlog space you get poor log information

[ https://issues.apache.org/jira/browse/CASSANDRA-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702444#comment-16702444 ] Ariel Weisberg commented on CASSANDRA-11323: This is great. You can consolidate it to a

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns are consistent for proxyhistograms and cfhistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Status: Ready to Commit (was: Patch Available) > Make Read and Write Latency

[jira] [Commented] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702486#comment-16702486 ] Jason Brown commented on CASSANDRA-14896: - [~aweisberg] is correct. On the third (and last)

[jira] [Updated] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-14896: --- Status: Ready to Commit (was: Patch Available) > 3.0 schema migration pulls

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns consistent for proxyhistograms and tablehistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Summary: Make Read and Write Latency columns consistent for proxyhistograms and

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns are consistent for proxyhistograms and tablehistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Summary: Make Read and Write Latency columns are consistent for proxyhistograms

cassandra git commit: Make Read and Write Latency columns consistent for proxyhistograms and tablehistograms

Repository: cassandra Updated Branches: refs/heads/trunk f2520d7a5 -> ff8906a6c Make Read and Write Latency columns consistent for proxyhistograms and tablehistograms Patch by Amanda R Debrot; Reviewed by Ariel Weisberg for CASSANDRA-11939 Project:

cassandra git commit: Send correct messaging version in internode messaging handshake's third message.

Repository: cassandra Updated Branches: refs/heads/trunk ff8906a6c -> c5dee08df Send correct messaging version in internode messaging handshake's third message. patch by jasobrown; reviewed by Ariel Weisberg for CASSANDRA-14896 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo

[jira] [Updated] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Brown updated CASSANDRA-14896: Resolution: Fixed Fix Version/s: (was: 3.0.x) 4.0

[jira] [Commented] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702503#comment-16702503 ] Jason Brown commented on CASSANDRA-14896: - The only utest that failed was

[jira] [Updated] (CASSANDRA-14761) Rename speculative_retry to match additional_write_policy

[ https://issues.apache.org/jira/browse/CASSANDRA-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-14761: --- Reviewers: Joseph Lynch Reviewer: Joseph Lynch > Rename speculative_retry

[jira] [Commented] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16702490#comment-16702490 ] Ariel Weisberg commented on CASSANDRA-14896: +1 to that fix. I've tested it and it

[jira] [Assigned] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg reassigned CASSANDRA-14896: -- Assignee: Jason Brown (was: Ariel Weisberg) Reviewers: Ariel

[jira] [Updated] (CASSANDRA-14896) 3.0 schema migration pulls from later version incompatible nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-14896: --- Status: Patch Available (was: Open) > 3.0 schema migration pulls from later

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns consistent for proxyhistograms and tablehistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as

[jira] [Updated] (CASSANDRA-11939) Make Read and Write Latency columns consistent for proxyhistograms and tablehistograms

[ https://issues.apache.org/jira/browse/CASSANDRA-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-11939: --- Fix Version/s: 4.0 > Make Read and Write Latency columns consistent for

[jira] [Updated] (CASSANDRA-14897) In mixed 3.x/4 version clusters write tracing and repair history information without new columns

[ https://issues.apache.org/jira/browse/CASSANDRA-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-14897: --- Status: Patch Available (was: Open) [Trunk