[jira] [Created] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers

Alexey Zotov created CASSANDRA-4768: --- Summary: Add separate max_hint_window_in_ms option for remote data centers Key: CASSANDRA-4768 URL: https://issues.apache.org/jira/browse/CASSANDRA-4768

[jira] [Updated] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers

[ https://issues.apache.org/jira/browse/CASSANDRA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zotov updated CASSANDRA-4768: Attachment: cassandra-1.2-4768-remote_hint_window.txt

[jira] [Updated] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers

[ https://issues.apache.org/jira/browse/CASSANDRA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zotov updated CASSANDRA-4768: Fix Version/s: 1.2.0 1.1.6 Add separate max_hint_window_in_ms

[jira] [Reopened] (CASSANDRA-4710) High key hashing overhead for index scans when using RandomPartitioner

[ https://issues.apache.org/jira/browse/CASSANDRA-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuki Morishita reopened CASSANDRA-4710: --- When I was trying to reproduce CASSANDRA-4733, I stumbled upon following error.

[jira] [Commented] (CASSANDRA-4684) Binary protocol: inform clients of schema changes

[ https://issues.apache.org/jira/browse/CASSANDRA-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470072#comment-13470072 ] Sylvain Lebresne commented on CASSANDRA-4684: - All I'm saying is that

[jira] [Commented] (CASSANDRA-4733) Last written key = current key exception when streaming

[ https://issues.apache.org/jira/browse/CASSANDRA-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470075#comment-13470075 ] Yuki Morishita commented on CASSANDRA-4733: --- I still cannot reproduce above

[jira] [Created] (CASSANDRA-4769) Prevent parallel hint delivery to the node

Alexey Zotov created CASSANDRA-4769: --- Summary: Prevent parallel hint delivery to the node Key: CASSANDRA-4769 URL: https://issues.apache.org/jira/browse/CASSANDRA-4769 Project: Cassandra

git commit: Fix support of collections in prepared statements

Updated Branches: refs/heads/trunk d54a93f2d - 8b00f3a25 Fix support of collections in prepared statements patch by slebresne; reviewed by jbellis for CASSANDRA-4739 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

git commit: Store more informations in peers table

Updated Branches: refs/heads/trunk 8b00f3a25 - d5ec013ce Store more informations in peers table patch by slebresne; reviewed by jbellis for CASSANDRA-4351 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/d5ec013c

buildbot failure in ASF Buildbot on cassandra-trunk

The Buildbot has detected a new failure on builder cassandra-trunk while building cassandra. Full details are available at: http://ci.apache.org/builders/cassandra-trunk/builds/1901 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build

[jira] [Commented] (CASSANDRA-4351) Consider storing more informations on peers in system tables

[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470087#comment-13470087 ] Sylvain Lebresne commented on CASSANDRA-4351: - Committed 0001 but holding

[jira] [Commented] (CASSANDRA-4763) SSTableLoader shouldn't get keyspace from path

[ https://issues.apache.org/jira/browse/CASSANDRA-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470088#comment-13470088 ] Sylvain Lebresne commented on CASSANDRA-4763: - bq. we require sstable

git commit: Fix comparison against IndexInterval in SSTR.getPosition()

Updated Branches: refs/heads/trunk d5ec013ce - 2a91a4818 Fix comparison against IndexInterval in SSTR.getPosition() Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2a91a481 Tree:

[jira] [Commented] (CASSANDRA-4710) High key hashing overhead for index scans when using RandomPartitioner

[ https://issues.apache.org/jira/browse/CASSANDRA-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470100#comment-13470100 ] Sylvain Lebresne commented on CASSANDRA-4710: - I agree, good catch. I went

[jira] [Resolved] (CASSANDRA-4710) High key hashing overhead for index scans when using RandomPartitioner

[ https://issues.apache.org/jira/browse/CASSANDRA-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-4710. - Resolution: Fixed High key hashing overhead for index scans when using

[jira] [Commented] (CASSANDRA-4710) High key hashing overhead for index scans when using RandomPartitioner

[ https://issues.apache.org/jira/browse/CASSANDRA-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470105#comment-13470105 ] Daniel Norberg commented on CASSANDRA-4710: --- Good catch.

git commit: Fix SystemTableTest

Updated Branches: refs/heads/trunk 2a91a4818 - b7716c76b Fix SystemTableTest Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/b7716c76 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/b7716c76 Diff:

git commit: (cql3) protect against null prepared variables (and avoid flooding the log on InvalidException errors)

Updated Branches: refs/heads/trunk b7716c76b - e232407ad (cql3) protect against null prepared variables (and avoid flooding the log on InvalidException errors) Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers

[ https://issues.apache.org/jira/browse/CASSANDRA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470367#comment-13470367 ] Jonathan Ellis commented on CASSANDRA-4768: --- I'm not sure if this is the

[jira] [Commented] (CASSANDRA-4684) Binary protocol: inform clients of schema changes

[ https://issues.apache.org/jira/browse/CASSANDRA-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470374#comment-13470374 ] Jonathan Ellis commented on CASSANDRA-4684: --- I still think this is premature

[jira] [Commented] (CASSANDRA-4684) Binary protocol: inform clients of schema changes

[ https://issues.apache.org/jira/browse/CASSANDRA-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470399#comment-13470399 ] Sylvain Lebresne commented on CASSANDRA-4684: - But it's very very little

[jira] [Created] (CASSANDRA-4770) (CQL3) data type not in lowercase are not handled correctly.

Sylvain Lebresne created CASSANDRA-4770: --- Summary: (CQL3) data type not in lowercase are not handled correctly. Key: CASSANDRA-4770 URL: https://issues.apache.org/jira/browse/CASSANDRA-4770

[jira] [Updated] (CASSANDRA-4770) (CQL3) data type not in lowercase are not handled correctly.

[ https://issues.apache.org/jira/browse/CASSANDRA-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-4770: Attachment: 4770.txt Trivial fix attached. (CQL3) data type

[Cassandra Wiki] Update of Partitioners by JonathanEllis

Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The Partitioners page has been changed by JonathanEllis: http://wiki.apache.org/cassandra/Partitioners New page: The Partitioner, along with the ReplicationStrategy, is responsible

[Cassandra Wiki] Update of Partitioners by JonathanEllis

Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The Partitioners page has been changed by JonathanEllis: http://wiki.apache.org/cassandra/Partitioners?action=diffrev1=1rev2=2 Cassandra supports the following partitioners, in

[jira] [Commented] (CASSANDRA-4766) ReverseCompaction

[ https://issues.apache.org/jira/browse/CASSANDRA-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470430#comment-13470430 ] T Jake Luciani commented on CASSANDRA-4766: --- You could do this with a new

[Cassandra Wiki] Update of Partitioners by JonathanEllis

Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The Partitioners page has been changed by JonathanEllis: http://wiki.apache.org/cassandra/Partitioners?action=diffrev1=2rev2=3 == RandomPartitioner == - Default partitioner in

[jira] [Commented] (CASSANDRA-4732) clean up unnecessary copies on KeyCache path

[ https://issues.apache.org/jira/browse/CASSANDRA-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470436#comment-13470436 ] Yuki Morishita commented on CASSANDRA-4732: --- +1 clean up

[Cassandra Wiki] Update of FAQ by JonathanEllis

Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The FAQ page has been changed by JonathanEllis: http://wiki.apache.org/cassandra/FAQ?action=diffrev1=150rev2=151 Comment: remove some obsolete questions and add Partitioners link

[jira] [Resolved] (CASSANDRA-4769) Prevent parallel hint delivery to the node

[ https://issues.apache.org/jira/browse/CASSANDRA-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-4769. --- Resolution: Not A Problem Set your hint throttle level appropriately instead of

[jira] [Commented] (CASSANDRA-4351) Consider storing more informations on peers in system tables

[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470442#comment-13470442 ] Jonathan Ellis commented on CASSANDRA-4351: --- No, I did mean instead, since

[jira] [Commented] (CASSANDRA-4770) (CQL3) data type not in lowercase are not handled correctly.

[ https://issues.apache.org/jira/browse/CASSANDRA-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470443#comment-13470443 ] Jonathan Ellis commented on CASSANDRA-4770: --- +1 (CQL3)

git commit: clean up unnecessary copy on KeyCache lookup patch by jbellis; reviewed by yukim for CASSANDRA-4732

Updated Branches: refs/heads/trunk e232407ad - e3f642b8c clean up unnecessary copy on KeyCache lookup patch by jbellis; reviewed by yukim for CASSANDRA-4732 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e3f642b8

[jira] [Commented] (CASSANDRA-4351) Consider storing more informations on peers in system tables

[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470450#comment-13470450 ] Sylvain Lebresne commented on CASSANDRA-4351: - Oh I see. Was mislead by

git commit: Correctly accept upper-case data type (CQL3)

Updated Branches: refs/heads/cassandra-1.1 0d44159e6 - 6eafeb2b0 Correctly accept upper-case data type (CQL3) patch by slebresne; reviewed by jbellis for CASSANDRA-4770 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[2/2] git commit: Correctly accept upper-case data type (CQL3)

Correctly accept upper-case data type (CQL3) patch by slebresne; reviewed by jbellis for CASSANDRA-4770 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/6eafeb2b Tree:

[1/2] git commit: Merge branch 'cassandra-1.1' into trunk

Updated Branches: refs/heads/trunk e3f642b8c - 1b56ad122 Merge branch 'cassandra-1.1' into trunk Conflicts: CHANGES.txt src/java/org/apache/cassandra/cql3/CFPropDefs.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-4351) Consider storing more informations on peers in system tables

[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470456#comment-13470456 ] Jonathan Ellis commented on CASSANDRA-4351: --- You're right, 0002 is useful

[jira] [Commented] (CASSANDRA-4705) Speculative execution for CL_ONE

[ https://issues.apache.org/jira/browse/CASSANDRA-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470461#comment-13470461 ] Chris Burroughs commented on CASSANDRA-4705: Looks like metrics-core

git commit: Save tokens as string in local and peers system table

Updated Branches: refs/heads/trunk 1b56ad122 - c2a8f1288 Save tokens as string in local and peers system table patch by slebresne; reviewed by jbellis for CASSANDRA-4351 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Resolved] (CASSANDRA-4351) Consider storing more informations on peers in system tables

[ https://issues.apache.org/jira/browse/CASSANDRA-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-4351. - Resolution: Fixed Reviewer: jbellis Assignee: Sylvain Lebresne

[jira] [Commented] (CASSANDRA-4705) Speculative execution for CL_ONE

[ https://issues.apache.org/jira/browse/CASSANDRA-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470470#comment-13470470 ] Jonathan Ellis commented on CASSANDRA-4705: --- Thanks Chris!

[jira] [Commented] (CASSANDRA-4684) Binary protocol: inform clients of schema changes

[ https://issues.apache.org/jira/browse/CASSANDRA-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470487#comment-13470487 ] Jonathan Ellis commented on CASSANDRA-4684: --- All right, +1

git commit: Adds binary protocol events for schema changes

Updated Branches: refs/heads/trunk c2a8f1288 - 11f7d7253 Adds binary protocol events for schema changes patch by slebresne; reviewed by jbellis for CASSANDRA-4684 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-4687) Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)

[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470512#comment-13470512 ] T Jake Luciani commented on CASSANDRA-4687: --- I am seeing something similar

git commit: Fix incorrect call of serializedSize

Updated Branches: refs/heads/trunk 11f7d7253 - 074f4befa Fix incorrect call of serializedSize Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/074f4bef Tree:

[jira] [Commented] (CASSANDRA-4687) Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)

[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470517#comment-13470517 ] T Jake Luciani commented on CASSANDRA-4687: --- On Pavel's advice I disabled

buildbot success in ASF Buildbot on cassandra-trunk

The Buildbot has detected a restored build on builder cassandra-trunk while building cassandra. Full details are available at: http://ci.apache.org/builders/cassandra-trunk/builds/1909 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build

[jira] [Commented] (CASSANDRA-4687) Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)

[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470531#comment-13470531 ] T Jake Luciani commented on CASSANDRA-4687: --- I've been loading data so it's

[jira] [Commented] (CASSANDRA-4769) Prevent parallel hint delivery to the node

[ https://issues.apache.org/jira/browse/CASSANDRA-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470583#comment-13470583 ] Alexey Zotov commented on CASSANDRA-4769: - Yes, it's the simplest way. But

[jira] [Created] (CASSANDRA-4771) Setting TTL to Integer.MAX causes columns to not be persisted.

Todd Nine created CASSANDRA-4771: Summary: Setting TTL to Integer.MAX causes columns to not be persisted. Key: CASSANDRA-4771 URL: https://issues.apache.org/jira/browse/CASSANDRA-4771 Project:

[jira] [Commented] (CASSANDRA-4687) Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)

[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470596#comment-13470596 ] T Jake Luciani commented on CASSANDRA-4687: --- One other thought. This only

[jira] [Commented] (CASSANDRA-4769) Prevent parallel hint delivery to the node

[ https://issues.apache.org/jira/browse/CASSANDRA-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470603#comment-13470603 ] Jonathan Ellis commented on CASSANDRA-4769: --- Hints are per node, not per

[jira] [Commented] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers

[ https://issues.apache.org/jira/browse/CASSANDRA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470628#comment-13470628 ] Alexey Zotov commented on CASSANDRA-4768: - I'll try to explain my motivation.

[jira] [Commented] (CASSANDRA-4157) Allow KS + CF names up to 48 characters

[ https://issues.apache.org/jira/browse/CASSANDRA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470654#comment-13470654 ] Chris Chiappone commented on CASSANDRA-4157: This actually causes a bunch

[jira] [Commented] (CASSANDRA-2749) fine-grained control over data directories

[ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470655#comment-13470655 ] Chris Chiappone commented on CASSANDRA-2749: This actually causes a bunch

[jira] [Created] (CASSANDRA-4772) HintedHandoff fails to deliver hints after first repaired node

Alexey Zotov created CASSANDRA-4772: --- Summary: HintedHandoff fails to deliver hints after first repaired node Key: CASSANDRA-4772 URL: https://issues.apache.org/jira/browse/CASSANDRA-4772 Project:

[jira] [Commented] (CASSANDRA-4157) Allow KS + CF names up to 48 characters

[ https://issues.apache.org/jira/browse/CASSANDRA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470670#comment-13470670 ] Jonathan Ellis commented on CASSANDRA-4157: --- They will need to fix that

[jira] [Commented] (CASSANDRA-4157) Allow KS + CF names up to 48 characters

[ https://issues.apache.org/jira/browse/CASSANDRA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470683#comment-13470683 ] Chris Chiappone commented on CASSANDRA-4157: We are attempting to upgrade

[jira] [Commented] (CASSANDRA-4723) Improve write timeout exceptions

[ https://issues.apache.org/jira/browse/CASSANDRA-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470688#comment-13470688 ] Jonathan Ellis commented on CASSANDRA-4723: --- +1 Improve

git commit: Add ability to use custom TServerFactory implementations patch by Jason Brown; reviewed by Pavel Yaskevich for CASSANDRA-4608

Updated Branches: refs/heads/cassandra-1.1 6eafeb2b0 - 8264eb21c Add ability to use custom TServerFactory implementations patch by Jason Brown; reviewed by Pavel Yaskevich for CASSANDRA-4608 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[1/2] git commit: merge from 1.1

Updated Branches: refs/heads/trunk 074f4befa - 6b83663ca merge from 1.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/6b83663c Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/6b83663c Diff:

[2/2] git commit: Add ability to use custom TServerFactory implementations patch by Jason Brown; reviewed by Pavel Yaskevich for CASSANDRA-4608

Add ability to use custom TServerFactory implementations patch by Jason Brown; reviewed by Pavel Yaskevich for CASSANDRA-4608 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8264eb21 Tree:

[jira] [Updated] (CASSANDRA-4667) optimize memtable deletions for batchlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4667: -- Attachment: 4667-handle-empty-flushes.txt fix attached. optimize

[jira] [Commented] (CASSANDRA-4687) Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)

[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470724#comment-13470724 ] Pavel Yaskevich commented on CASSANDRA-4687: [~tpatterson] Can you try to

[jira] [Commented] (CASSANDRA-4667) optimize memtable deletions for batchlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470751#comment-13470751 ] Aleksey Yeschenko commented on CASSANDRA-4667: -- The patch works. +1

[jira] [Comment Edited] (CASSANDRA-4667) optimize memtable deletions for batchlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470751#comment-13470751 ] Aleksey Yeschenko edited comment on CASSANDRA-4667 at 10/5/12 10:47 PM:

[jira] [Commented] (CASSANDRA-4050) cassandra unnecessarily holds file locks on snapshot files

[ https://issues.apache.org/jira/browse/CASSANDRA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470759#comment-13470759 ] Alexander Kashirin commented on CASSANDRA-4050: --- I have the same problem

[jira] [Updated] (CASSANDRA-4657) cql version race condition with rpc_server_type: sync

[ https://issues.apache.org/jira/browse/CASSANDRA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4657: -- Reviewer: dbrosius Priority: Minor (was: Major) Affects

[jira] [Commented] (CASSANDRA-4657) cql version race condition with rpc_server_type: sync

[ https://issues.apache.org/jira/browse/CASSANDRA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470899#comment-13470899 ] Jonathan Ellis commented on CASSANDRA-4657: --- Thanks Emmanuel! Your patch

[jira] [Updated] (CASSANDRA-4050) Unable to remove snapshot files on Windows while original sstables are live

[ https://issues.apache.org/jira/browse/CASSANDRA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4050: -- Affects Version/s: (was: 1.0.8) Summary: Unable to remove

[jira] [Commented] (CASSANDRA-4050) cassandra unnecessarily holds file locks on snapshot files

[ https://issues.apache.org/jira/browse/CASSANDRA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470901#comment-13470901 ] Jonathan Ellis commented on CASSANDRA-4050: --- Right, so NTFS is locking the

git commit: handle empty flushes of batchlog memtable patch by jbellis; tested by Aleksey Yeschenko for CASSANDRA-4667

Updated Branches: refs/heads/trunk 6b83663ca - 801d7d3f5 handle empty flushes of batchlog memtable patch by jbellis; tested by Aleksey Yeschenko for CASSANDRA-4667 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Resolved] (CASSANDRA-4667) optimize memtable deletions for batchlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-4667. --- Resolution: Fixed committed optimize memtable deletions for

[jira] [Commented] (CASSANDRA-4157) Allow KS + CF names up to 48 characters

[ https://issues.apache.org/jira/browse/CASSANDRA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470905#comment-13470905 ] Jonathan Ellis commented on CASSANDRA-4157: --- My mistake. The distinction is

[jira] [Created] (CASSANDRA-4773) CQL shell not reflecting latest data when timestamp is passed as part of insert statements

Ananth Gundabattula created CASSANDRA-4773: -- Summary: CQL shell not reflecting latest data when timestamp is passed as part of insert statements Key: CASSANDRA-4773 URL:

[jira] [Commented] (CASSANDRA-4657) cql version race condition with rpc_server_type: sync

[ https://issues.apache.org/jira/browse/CASSANDRA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470921#comment-13470921 ] Dave Brosius commented on CASSANDRA-4657: - +1 patch lgtm.