[jira] [Comment Edited] (CASSANDRA-10371) Decommissioned nodes can remain in gossip

[ https://issues.apache.org/jira/browse/CASSANDRA-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066681#comment-15066681 ] Didier edited comment on CASSANDRA-10371 at 12/21/15 4:43 PM: -- Hi

[jira] [Commented] (CASSANDRA-10371) Decommissioned nodes can remain in gossip

[ https://issues.apache.org/jira/browse/CASSANDRA-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066681#comment-15066681 ] Didier commented on CASSANDRA-10371: Hi Stefania, Thanks to your quick answer. I attach TRACE

[jira] [Commented] (CASSANDRA-10906) List index out of range

[ https://issues.apache.org/jira/browse/CASSANDRA-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066654#comment-15066654 ] Jim Witschey commented on CASSANDRA-10906: -- Thank you for the report. Could you please

[jira] [Updated] (CASSANDRA-10906) List index out of range

[ https://issues.apache.org/jira/browse/CASSANDRA-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-10906: - Component/s: (was: CQL) Tools > List index out of range >

[jira] [Updated] (CASSANDRA-10906) List index out of range

[ https://issues.apache.org/jira/browse/CASSANDRA-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-10906: - Environment: java version "1.8.0_66", 64-bit (was: cqlsh:fd> show version; [cqlsh

[jira] [Updated] (CASSANDRA-10906) List index out of range

[ https://issues.apache.org/jira/browse/CASSANDRA-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-10906: - Flags: (was: Important) > List index out of range > --- > >

[jira] [Updated] (CASSANDRA-10877) Unable to read obsolete message version 1; The earliest version supported is 2.0.0

[ https://issues.apache.org/jira/browse/CASSANDRA-10877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-10877: - Description: I used cassandra version 2.1.2, but I get some error about that:

[jira] [Updated] (CASSANDRA-10887) Pending range calculator gives wrong pending ranges for moves

[ https://issues.apache.org/jira/browse/CASSANDRA-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10887: - Reviewer: Branimir Lambov > Pending range calculator gives wrong pending

[jira] [Updated] (CASSANDRA-10887) Pending range calculator gives wrong pending ranges for moves

[ https://issues.apache.org/jira/browse/CASSANDRA-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-10887: -- Fix Version/s: 3.x 3.0.x 2.2.x

[jira] [Commented] (CASSANDRA-10864) Dropped mutations high until cluster restart

[ https://issues.apache.org/jira/browse/CASSANDRA-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066688#comment-15066688 ] Jim Witschey commented on CASSANDRA-10864: -- Here:

[jira] [Updated] (CASSANDRA-10854) cqlsh COPY FROM csv having line with more than one consecutive ',' delimiter is throwing 'list index out of range'

[ https://issues.apache.org/jira/browse/CASSANDRA-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-10854: - Description: cqlsh COPY FROM csv having line with more than one consecutive ','

[jira] [Commented] (CASSANDRA-7464) Replace sstable2json and json2sstable

[ https://issues.apache.org/jira/browse/CASSANDRA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066699#comment-15066699 ] Joshua McKenzie commented on CASSANDRA-7464: [~cnlwsu] / [~andrew.tolbert]: How much work

[jira] [Commented] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds

[ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066524#comment-15066524 ] Stefania commented on CASSANDRA-8072: - Building on [~brandon.williams] previous analysis but

[jira] [Comment Edited] (CASSANDRA-10801) Unexplained inconsistent data with Cassandra 2.1

[ https://issues.apache.org/jira/browse/CASSANDRA-10801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066461#comment-15066461 ] Maor Cohen edited comment on CASSANDRA-10801 at 12/21/15 3:02 PM: --

[2/3] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

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

[jira] [Updated] (CASSANDRA-10850) v4 spec has tons of grammatical mistakes

[ https://issues.apache.org/jira/browse/CASSANDRA-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10850: - Assignee: Sandeep Tamhankar > v4 spec has tons of grammatical mistakes >

[jira] [Commented] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds

[ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066601#comment-15066601 ] Stefania commented on CASSANDRA-8072: - In fact we don't need to extend the shadow round since

[jira] [Comment Edited] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds

[ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066524#comment-15066524 ] Stefania edited comment on CASSANDRA-8072 at 12/21/15 3:54 PM: --- Building

[2/2] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

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

[1/3] cassandra git commit: Fix grammatical errors and imprecisions in native protocol spec

Repository: cassandra Updated Branches: refs/heads/trunk 565799c28 -> 43f8f8bb3 Fix grammatical errors and imprecisions in native protocol spec patch by stamhankar999; reviewed by slebresne for CASSANDRA-10850 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[3/3] cassandra git commit: Merge branch 'cassandra-3.0' into trunk

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

[1/2] cassandra git commit: Fix grammatical errors and imprecisions in native protocol spec

Repository: cassandra Updated Branches: refs/heads/cassandra-3.0 67fd42fd3 -> adc9a241e Fix grammatical errors and imprecisions in native protocol spec patch by stamhankar999; reviewed by slebresne for CASSANDRA-10850 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows

[ https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066522#comment-15066522 ] Carl Yeksigian commented on CASSANDRA-10910: I can reproduce this bug on a single

[jira] [Commented] (CASSANDRA-10686) cqlsh schema refresh on timeout dtest is flaky

[ https://issues.apache.org/jira/browse/CASSANDRA-10686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066543#comment-15066543 ] Joel Knighton commented on CASSANDRA-10686: --- Fixing upstream also works for me with the

[jira] [Commented] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds

[ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066554#comment-15066554 ] Stefania commented on CASSANDRA-8072: - Forgot to mention also another obvious way to go around

[jira] [Commented] (CASSANDRA-8844) Change Data Capture (CDC)

[ https://issues.apache.org/jira/browse/CASSANDRA-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066606#comment-15066606 ] Tupshin Harper commented on CASSANDRA-8844: --- It is designed to be RF copies for redundancy

[jira] [Commented] (CASSANDRA-9303) Match cassandra-loader options in COPY FROM

[ https://issues.apache.org/jira/browse/CASSANDRA-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066557#comment-15066557 ] Paulo Motta commented on CASSANDRA-9303: bq. That's correct, copy-to* sections are not read in

cassandra git commit: Fix grammatical errors and imprecisions in native protocol spec

Repository: cassandra Updated Branches: refs/heads/cassandra-2.2 df49cec1c -> 8565ca89a Fix grammatical errors and imprecisions in native protocol spec patch by stamhankar999; reviewed by slebresne for CASSANDRA-10850 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-10876) Alter behavior of batch WARN and fail on single partition batches

[ https://issues.apache.org/jira/browse/CASSANDRA-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066710#comment-15066710 ] Patrick McFadin commented on CASSANDRA-10876: - [~firstprayer] if you would like to take

[jira] [Commented] (CASSANDRA-10907) Nodetool snapshot should provide an option to skip flushing

[ https://issues.apache.org/jira/browse/CASSANDRA-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066715#comment-15066715 ] Nick Bailey commented on CASSANDRA-10907: - Just wondering what scenarios skipping flushing

[jira] [Updated] (CASSANDRA-9842) Inconsistent behavior for '= null' conditions on static columns

[ https://issues.apache.org/jira/browse/CASSANDRA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-9842: Assignee: Benjamin Lerer > Inconsistent behavior for '= null' conditions on

[jira] [Updated] (CASSANDRA-9842) Inconsistent behavior for '= null' conditions on static columns

[ https://issues.apache.org/jira/browse/CASSANDRA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-9842: Fix Version/s: 3.x 3.0.x 2.2.x

[jira] [Updated] (CASSANDRA-9842) Inconsistent behavior for '= null' conditions on static columns

[ https://issues.apache.org/jira/browse/CASSANDRA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-9842: Summary: Inconsistent behavior for '= null' conditions on static columns (was:

[jira] [Commented] (CASSANDRA-9842) Creation of partition and update of static columns in the same LWT fails

[ https://issues.apache.org/jira/browse/CASSANDRA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066724#comment-15066724 ] Sylvain Lebresne commented on CASSANDRA-9842: - You're right, there is an inconsistency

[jira] [Commented] (CASSANDRA-9977) Support counter-columns for native aggregates (sum,avg,max,min)

[ https://issues.apache.org/jira/browse/CASSANDRA-9977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066768#comment-15066768 ] Robert Stupp commented on CASSANDRA-9977: - Updated the 2.2 and 3.0 branches (trunk is just a

[jira] [Commented] (CASSANDRA-10866) Column Family should expose count metrics for dropped mutations.

[ https://issues.apache.org/jira/browse/CASSANDRA-10866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066779#comment-15066779 ] Anubhav Kale commented on CASSANDRA-10866: -- Any updates here ? > Column Family should

[jira] [Commented] (CASSANDRA-10907) Nodetool snapshot should provide an option to skip flushing

[ https://issues.apache.org/jira/browse/CASSANDRA-10907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066788#comment-15066788 ] Anubhav Kale commented on CASSANDRA-10907: -- We plan to move backups outside the nodes. So,

<    1   2