[jira] [Commented] (CASSANDRA-8081) AssertionError with 2ndary indexes

[ https://issues.apache.org/jira/browse/CASSANDRA-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167956#comment-14167956 ] Jeremiah Jordan commented on CASSANDRA-8081: Native 2i Index searches only

[jira] [Commented] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167896#comment-14167896 ] T Jake Luciani commented on CASSANDRA-8054: --- +1 fixes the issue for me. can

[jira] [Created] (CASSANDRA-8103) Secondary Indices for Static Columns

Ron Cohen created CASSANDRA-8103: Summary: Secondary Indices for Static Columns Key: CASSANDRA-8103 URL: https://issues.apache.org/jira/browse/CASSANDRA-8103 Project: Cassandra Issue Type: Ne

[jira] [Updated] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-8054: - Fix Version/s: 2.0.11 > EXECUTE request with skipMetadata=false gets no metada

[jira] [Commented] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167789#comment-14167789 ] Aleksey Yeschenko commented on CASSANDRA-8054: -- Same is probably true for

[jira] [Updated] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-8054: - Attachment: 8054-fix.txt > EXECUTE request with skipMetadata=false gets no met

[jira] [Reopened] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko reopened CASSANDRA-8054: -- > EXECUTE request with skipMetadata=false gets no metadata in response > ---

[jira] [Commented] (CASSANDRA-8054) EXECUTE request with skipMetadata=false gets no metadata in response

[ https://issues.apache.org/jira/browse/CASSANDRA-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167776#comment-14167776 ] Aleksey Yeschenko commented on CASSANDRA-8054: -- Reopening because CASSAND

[jira] [Resolved] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko resolved CASSANDRA-7923. -- Resolution: Fixed Assignee: Tyler Hobbs (was: Aleksey Yeschenko) Clos

[jira] [Commented] (CASSANDRA-8097) Hi Team, I am new to cassandr seeing folloiwng errors in cassandra system.log file.NO_SOURCE_FILE (line 0) Thrift operation queue is full, discarding thrift operati

[ https://issues.apache.org/jira/browse/CASSANDRA-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167706#comment-14167706 ] Swapnil Bhisey commented on CASSANDRA-8097: --- What do you thing must have mes

[jira] [Comment Edited] (CASSANDRA-5940) Create a ppa to make Debian/Ubuntu installation easier

[ https://issues.apache.org/jira/browse/CASSANDRA-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167516#comment-14167516 ] Michael Shuler edited comment on CASSANDRA-5940 at 10/10/14 10:33 PM: --

[jira] [Commented] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167633#comment-14167633 ] graham sanderson commented on CASSANDRA-7546: - Just to be clear from the g

[jira] [Commented] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167630#comment-14167630 ] Aleksey Yeschenko commented on CASSANDRA-7923: -- FWIW, there is nothing wr

[jira] [Comment Edited] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167613#comment-14167613 ] graham sanderson edited comment on CASSANDRA-7546 at 10/10/14 10:03 PM:

[jira] [Comment Edited] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167613#comment-14167613 ] graham sanderson edited comment on CASSANDRA-7546 at 10/10/14 10:02 PM:

[jira] [Updated] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] graham sanderson updated CASSANDRA-7546: Attachment: graph4_7546.png See previous comment for discussion (note I also rea

[jira] [Commented] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167613#comment-14167613 ] graham sanderson commented on CASSANDRA-7546: - Sorry [~yukim], I somehow m

[jira] [Commented] (CASSANDRA-8101) Invalid ASCII and UTF-8 chars not rejected in CQL string literals

[ https://issues.apache.org/jira/browse/CASSANDRA-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167608#comment-14167608 ] Tyler Hobbs commented on CASSANDRA-8101: Pull request for netty opened here: h

[jira] [Updated] (CASSANDRA-8101) Invalid ASCII and UTF-8 chars not rejected in CQL string literals

[ https://issues.apache.org/jira/browse/CASSANDRA-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-8101: --- Attachment: 8101.txt The ascii problem was exactly as the descriptions says, and the chang

[jira] [Commented] (CASSANDRA-4762) Support IN clause for any clustering column

[ https://issues.apache.org/jira/browse/CASSANDRA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167562#comment-14167562 ] Constance Eustace commented on CASSANDRA-4762: -- So does 3.0 drop this bac

[jira] [Assigned] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko reassigned CASSANDRA-7923: Assignee: Aleksey Yeschenko (was: Tyler Hobbs) > When preparing a stat

[jira] [Commented] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167519#comment-14167519 ] T Jake Luciani commented on CASSANDRA-7923: --- Right... It shouldn't hang, T

[jira] [Commented] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167518#comment-14167518 ] Robert Stupp commented on CASSANDRA-7923: - bq. client driver is throwing an as

[jira] [Commented] (CASSANDRA-5940) Create a ppa to make Debian/Ubuntu installation easier

[ https://issues.apache.org/jira/browse/CASSANDRA-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167516#comment-14167516 ] Michael Shuler commented on CASSANDRA-5940: --- These PPAs may go away, be chan

[jira] [Updated] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] T Jake Luciani updated CASSANDRA-7923: -- Attachment: 7923-test.txt Test to reproduce the issue > When preparing a statement,

[jira] [Commented] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167491#comment-14167491 ] T Jake Luciani commented on CASSANDRA-7923: --- It seems like the underlying is

[jira] [Commented] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167456#comment-14167456 ] Robert Stupp commented on CASSANDRA-7923: - bq. This breaks clients that discon

[2/3] git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Conflicts: CHANGES.txt src/java/org/apache/cassandra/db/DefsTables.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/42582ecd Tree: http://git-wip-us.

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

Merge branch 'cassandra-2.1' into trunk Conflicts: src/java/org/apache/cassandra/db/DefsTables.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/fa592a46 Tree: http://git-wip-us.apache.org/repos/asf/cassand

[1/3] git commit: Fix merging schemas with re-dropped keyspaces

Repository: cassandra Updated Branches: refs/heads/trunk 47863bc32 -> fa592a46b Fix merging schemas with re-dropped keyspaces patch by Aleksey Yeschenko; reviewed by Pavel Yaskevich for CASSANDRA-7256 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.ap

[jira] [Updated] (CASSANDRA-8102) cassandra-cli and cqlsh report two different values for a setting, partially update it and partially report it

[ https://issues.apache.org/jira/browse/CASSANDRA-8102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Haggerty updated CASSANDRA-8102: -- Description: cassandra-cli updates and prints out a min_compaction_threshold that is

[jira] [Created] (CASSANDRA-8102) cassandra-cli and cqlsh report two different values for a setting, partially update it and partially report it

Peter Haggerty created CASSANDRA-8102: - Summary: cassandra-cli and cqlsh report two different values for a setting, partially update it and partially report it Key: CASSANDRA-8102 URL: https://issues.apache.or

[jira] [Updated] (CASSANDRA-7317) Repair range validation is too strict

[ https://issues.apache.org/jira/browse/CASSANDRA-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremiah Jordan updated CASSANDRA-7317: --- Summary: Repair range validation is too strict (was: Repair range validation and

[jira] [Reopened] (CASSANDRA-7923) When preparing a statement, do not parse the provided string if we already have the parsed statement cached

[ https://issues.apache.org/jira/browse/CASSANDRA-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] T Jake Luciani reopened CASSANDRA-7923: --- This breaks clients that disconnect and re-prepare statements You can see it break b

[1/2] git commit: Fix merging schemas with re-dropped keyspaces

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 e711929e7 -> 42582ecd4 Fix merging schemas with re-dropped keyspaces patch by Aleksey Yeschenko; reviewed by Pavel Yaskevich for CASSANDRA-7256 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-w

[2/2] git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Conflicts: CHANGES.txt src/java/org/apache/cassandra/db/DefsTables.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/42582ecd Tree: http://git-wip-us.

[jira] [Updated] (CASSANDRA-8101) Invalid ASCII and UTF-8 chars not rejected in CQL string literals

[ https://issues.apache.org/jira/browse/CASSANDRA-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-8101: --- Reproduced In: 2.1.0, 2.0.10 > Invalid ASCII and UTF-8 chars not rejected in CQL string li

[jira] [Created] (CASSANDRA-8101) Invalid ASCII and UTF-8 chars not rejected in CQL string literals

Tyler Hobbs created CASSANDRA-8101: -- Summary: Invalid ASCII and UTF-8 chars not rejected in CQL string literals Key: CASSANDRA-8101 URL: https://issues.apache.org/jira/browse/CASSANDRA-8101 Project:

[jira] [Commented] (CASSANDRA-8097) Hi Team, I am new to cassandr seeing folloiwng errors in cassandra system.log file.NO_SOURCE_FILE (line 0) Thrift operation queue is full, discarding thrift operati

[ https://issues.apache.org/jira/browse/CASSANDRA-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166983#comment-14166983 ] Tyler Hobbs commented on CASSANDRA-8097: Well, I don't know what to say about

[jira] [Commented] (CASSANDRA-8097) Hi Team, I am new to cassandr seeing folloiwng errors in cassandra system.log file.NO_SOURCE_FILE (line 0) Thrift operation queue is full, discarding thrift operati

[ https://issues.apache.org/jira/browse/CASSANDRA-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166979#comment-14166979 ] Swapnil Bhisey commented on CASSANDRA-8097: --- I am checking correct log. ca

[jira] [Commented] (CASSANDRA-8097) Hi Team, I am new to cassandr seeing folloiwng errors in cassandra system.log file.NO_SOURCE_FILE (line 0) Thrift operation queue is full, discarding thrift operati

[ https://issues.apache.org/jira/browse/CASSANDRA-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166930#comment-14166930 ] Tyler Hobbs commented on CASSANDRA-8097: The log message in the description is

[jira] [Created] (CASSANDRA-8100) Remove payload size from intra-cluster messages

Sylvain Lebresne created CASSANDRA-8100: --- Summary: Remove payload size from intra-cluster messages Key: CASSANDRA-8100 URL: https://issues.apache.org/jira/browse/CASSANDRA-8100 Project: Cassandra

git commit: Fix merging schemas with re-dropped keyspaces

Repository: cassandra Updated Branches: refs/heads/cassandra-2.0 b7adf9810 -> 0393c3063 Fix merging schemas with re-dropped keyspaces patch by Aleksey Yeschenko; reviewed by Pavel Yaskevich for CASSANDRA-7256 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-w

[jira] [Commented] (CASSANDRA-8099) Refactor and modernize the storage engine

[ https://issues.apache.org/jira/browse/CASSANDRA-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166912#comment-14166912 ] Sylvain Lebresne commented on CASSANDRA-8099: - For information, and to hop

[jira] [Created] (CASSANDRA-8099) Refactor and modernize the storage engine

Sylvain Lebresne created CASSANDRA-8099: --- Summary: Refactor and modernize the storage engine Key: CASSANDRA-8099 URL: https://issues.apache.org/jira/browse/CASSANDRA-8099 Project: Cassandra

[jira] [Comment Edited] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166901#comment-14166901 ] Andrew S edited comment on CASSANDRA-8089 at 10/10/14 2:27 PM: -

[jira] [Comment Edited] (CASSANDRA-8084) GossipFilePropertySnitch and EC2MultiRegionSnitch when used in AWS/GCE clusters doesnt use the PRIVATE IPS for Intra-DC communications - When running nodetool

[ https://issues.apache.org/jira/browse/CASSANDRA-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166908#comment-14166908 ] J.B. Langston edited comment on CASSANDRA-8084 at 10/10/14 2:26 PM:

[jira] [Comment Edited] (CASSANDRA-8084) GossipFilePropertySnitch and EC2MultiRegionSnitch when used in AWS/GCE clusters doesnt use the PRIVATE IPS for Intra-DC communications - When running nodetool

[ https://issues.apache.org/jira/browse/CASSANDRA-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166908#comment-14166908 ] J.B. Langston edited comment on CASSANDRA-8084 at 10/10/14 2:25 PM:

[jira] [Commented] (CASSANDRA-8084) GossipFilePropertySnitch and EC2MultiRegionSnitch when used in AWS/GCE clusters doesnt use the PRIVATE IPS for Intra-DC communications - When running nodetool repai

[ https://issues.apache.org/jira/browse/CASSANDRA-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166908#comment-14166908 ] J.B. Langston commented on CASSANDRA-8084: -- I tested and it appears to work.

[jira] [Comment Edited] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166901#comment-14166901 ] Andrew S edited comment on CASSANDRA-8089 at 10/10/14 2:21 PM: -

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166901#comment-14166901 ] Andrew S commented on CASSANDRA-8089: - > looks like you have a 110GB partition in

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

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

[1/2] git commit: Fix counters in supercolumns during live upgrades from 1.2

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 1bae25ace -> e711929e7 Fix counters in supercolumns during live upgrades from 1.2 patch by Aleksey Yeschenko; reviewed by Sylvain Lebresne for CASSANDRA-7188 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit

[1/3] git commit: Fix counters in supercolumns during live upgrades from 1.2

Repository: cassandra Updated Branches: refs/heads/trunk 810c2d5fe -> 47863bc32 Fix counters in supercolumns during live upgrades from 1.2 patch by Aleksey Yeschenko; reviewed by Sylvain Lebresne for CASSANDRA-7188 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http:/

[2/3] git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Conflicts: CHANGES.txt src/java/org/apache/cassandra/db/CounterUpdateColumn.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e711929e Tree: http://gi

[2/2] git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Conflicts: CHANGES.txt src/java/org/apache/cassandra/db/CounterUpdateColumn.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e711929e Tree: http://gi

[jira] [Commented] (CASSANDRA-8091) Stress tool creates too large batches

[ https://issues.apache.org/jira/browse/CASSANDRA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166844#comment-14166844 ] T Jake Luciani commented on CASSANDRA-8091: --- bq. Why is stress inserting log

git commit: Fix counters in supercolumns during live upgrades from 1.2

Repository: cassandra Updated Branches: refs/heads/cassandra-2.0 cced4ba15 -> b7adf9810 Fix counters in supercolumns during live upgrades from 1.2 patch by Aleksey Yeschenko; reviewed by Sylvain Lebresne for CASSANDRA-7188 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit

[jira] [Commented] (CASSANDRA-7970) JSON support for CQL

[ https://issues.apache.org/jira/browse/CASSANDRA-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166841#comment-14166841 ] Aleksey Yeschenko commented on CASSANDRA-7970: -- +1 as well > JSON suppor

[jira] [Updated] (CASSANDRA-6602) Compaction improvements to optimize time series data

[ https://issues.apache.org/jira/browse/CASSANDRA-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-6602: --- Fix Version/s: (was: 3.0) 2.0.11 > Compaction improvements

[jira] [Commented] (CASSANDRA-7927) Kill daemon on any disk error

[ https://issues.apache.org/jira/browse/CASSANDRA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166813#comment-14166813 ] John Sumsion commented on CASSANDRA-7927: - Looks great! The compromise on che

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166700#comment-14166700 ] Marcus Eriksson commented on CASSANDRA-8089: looks like you have a 110GB p

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166698#comment-14166698 ] Andrew S commented on CASSANDRA-8089: - > nodetool cfstats Table: table_with_tombs

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166686#comment-14166686 ] Marcus Eriksson commented on CASSANDRA-8089: and 'nodetool cfstats' should

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1414#comment-1414 ] Marcus Eriksson commented on CASSANDRA-8089: perhaps, do you have any idea

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166657#comment-14166657 ] Andrew S commented on CASSANDRA-8089: - Same error message on all nodes and tables

[jira] [Commented] (CASSANDRA-4886) Remote ColumnFamilyInputFormat

[ https://issues.apache.org/jira/browse/CASSANDRA-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166651#comment-14166651 ] mck commented on CASSANDRA-4886: AFAIK everything thrift related is frozen :( so i pre

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166648#comment-14166648 ] Marcus Eriksson commented on CASSANDRA-8089: looks like it could be relate

[jira] [Created] (CASSANDRA-8098) Allow CqlInputFormat to be restricted to more than one data-center

mck created CASSANDRA-8098: -- Summary: Allow CqlInputFormat to be restricted to more than one data-center Key: CASSANDRA-8098 URL: https://issues.apache.org/jira/browse/CASSANDRA-8098 Project: Cassandra

[jira] [Commented] (CASSANDRA-2388) ColumnFamilyRecordReader fails for a given split because a host is down, even if records could reasonably be read from other replica.

[ https://issues.apache.org/jira/browse/CASSANDRA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166644#comment-14166644 ] mck commented on CASSANDRA-2388: [~pkolaczk] + [~pauloricardomg], AFAIK everything t

[jira] [Commented] (CASSANDRA-7188) Wrong class type: class org.apache.cassandra.db.Column in CounterColumn.reconcile

[ https://issues.apache.org/jira/browse/CASSANDRA-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166587#comment-14166587 ] Sylvain Lebresne commented on CASSANDRA-7188: - +1 for the patch (but it wo

[jira] [Comment Edited] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166563#comment-14166563 ] Andrew S edited comment on CASSANDRA-8089 at 10/10/14 9:03 AM: -

[jira] [Comment Edited] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166563#comment-14166563 ] Andrew S edited comment on CASSANDRA-8089 at 10/10/14 8:46 AM: -

[jira] [Commented] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166563#comment-14166563 ] Andrew S commented on CASSANDRA-8089: - We are also getting the following exception

[jira] [Updated] (CASSANDRA-8089) Invalid tombstone warnings / exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew S updated CASSANDRA-8089: Description: Hey, We are having a strange issue with tombstone warnings which look like this: