[jira] [Commented] (CASSANDRA-4131) Integrate Hive support to be in core cassandra

[ https://issues.apache.org/jira/browse/CASSANDRA-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699835#comment-13699835 ] Cyril Scetbon commented on CASSANDRA-4131: -- bq. getting it to work with CQL3

[jira] [Created] (CASSANDRA-5723) the datetime comparetion is not right in cql3!

zhouhero created CASSANDRA-5723: --- Summary: the datetime comparetion is not right in cql3! Key: CASSANDRA-5723 URL: https://issues.apache.org/jira/browse/CASSANDRA-5723 Project: Cassandra Issue

[jira] [Updated] (CASSANDRA-5723) the datetime compare is not right in cql3!

[ https://issues.apache.org/jira/browse/CASSANDRA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhouhero updated CASSANDRA-5723: Summary: the datetime compare is not right in cql3! (was: the datetime comparetion is not righ

[jira] [Updated] (CASSANDRA-5723) the datetime comparetion is not right in cql3!

[ https://issues.apache.org/jira/browse/CASSANDRA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhouhero updated CASSANDRA-5723: Description: - this bug can be confirmed by fellow: 1.create table like fellow: create table

[jira] [Updated] (CASSANDRA-5723) the datetime compare not right in cql3!

[ https://issues.apache.org/jira/browse/CASSANDRA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhouhero updated CASSANDRA-5723: Summary: the datetime compare not right in cql3! (was: the datetime compare is not right in cq

[jira] [Commented] (CASSANDRA-5677) Performance improvements of RangeTombstones/IntervalTree

[ https://issues.apache.org/jira/browse/CASSANDRA-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700035#comment-13700035 ] Sylvain Lebresne commented on CASSANDRA-5677: - So first, let's remark how

[jira] [Created] (CASSANDRA-5724) Cassandra upgrade

Or Sher created CASSANDRA-5724: -- Summary: Cassandra upgrade Key: CASSANDRA-5724 URL: https://issues.apache.org/jira/browse/CASSANDRA-5724 Project: Cassandra Issue Type: Improvement

[jira] [Updated] (CASSANDRA-5724) Timeouts for slice/rangeslice queries while some nodes versions are lower than 1.2 and some higher.

[ https://issues.apache.org/jira/browse/CASSANDRA-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Or Sher updated CASSANDRA-5724: --- Component/s: Core Description: When doing a rolling upgrade from 1.0.* or 1.1.* t

[jira] [Created] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

Sergio Bossa created CASSANDRA-5725: --- Summary: Silently failing messages in case of schema not fully propagated Key: CASSANDRA-5725 URL: https://issues.apache.org/jira/browse/CASSANDRA-5725 Project:

git commit: Fix testing CQL2 key aliases

Updated Branches: refs/heads/trunk 67ccdabfe -> b7e49b3ab Fix testing CQL2 key aliases Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/b7e49b3a Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/b7e49b3a D

[jira] [Commented] (CASSANDRA-5702) ALTER RENAME is broken in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700069#comment-13700069 ] Sylvain Lebresne commented on CASSANDRA-5702: - Had forgot a toUppercase()

[jira] [Resolved] (CASSANDRA-5702) ALTER RENAME is broken in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-5702. - Resolution: Fixed > ALTER RENAME is broken in trunk > ---

[jira] [Commented] (CASSANDRA-5667) Change timestamps used in CAS ballot proposals to be more resilient to clock skew

[ https://issues.apache.org/jira/browse/CASSANDRA-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700073#comment-13700073 ] Sylvain Lebresne commented on CASSANDRA-5667: - lgtm, +1 >

[jira] [Commented] (CASSANDRA-5677) Performance improvements of RangeTombstones/IntervalTree

[ https://issues.apache.org/jira/browse/CASSANDRA-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700093#comment-13700093 ] Fabien Rousseau commented on CASSANDRA-5677: I had a quick look at the pat

[jira] [Reopened] (CASSANDRA-5619) CAS UPDATE for a lost race: save round trip by returning column values

[ https://issues.apache.org/jira/browse/CASSANDRA-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne reopened CASSANDRA-5619: - I think I'm having a problem getting that issue right. This is now CQL3 that is

[jira] [Updated] (CASSANDRA-5715) CAS on 'primary key only' table

[ https://issues.apache.org/jira/browse/CASSANDRA-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5715: Attachment: 0002-Support-updating-the-PK-only.txt 0001-Condition

[jira] [Commented] (CASSANDRA-5723) the datetime compare not right in cql3!

[ https://issues.apache.org/jira/browse/CASSANDRA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700164#comment-13700164 ] Sylvain Lebresne commented on CASSANDRA-5723: - bq. it should be fellow No

[jira] [Commented] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

[ https://issues.apache.org/jira/browse/CASSANDRA-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700177#comment-13700177 ] Jonathan Ellis commented on CASSANDRA-5725: --- This is working as designed. W

[jira] [Commented] (CASSANDRA-5677) Performance improvements of RangeTombstones/IntervalTree

[ https://issues.apache.org/jira/browse/CASSANDRA-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700181#comment-13700181 ] Jonathan Ellis commented on CASSANDRA-5677: --- Adding switches doesn't really

[jira] [Commented] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

[ https://issues.apache.org/jira/browse/CASSANDRA-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700187#comment-13700187 ] Sergio Bossa commented on CASSANDRA-5725: - Well, in an ideal world, given C* h

[jira] [Commented] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

[ https://issues.apache.org/jira/browse/CASSANDRA-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700213#comment-13700213 ] Jonathan Ellis commented on CASSANDRA-5725: --- bq. Finally, a trivial one may

git commit: use max(current time from system clock, inProgress + 1) as CAS ballot patch by jbellis; reviewed by slebresne for CASSANDRA-5667

Updated Branches: refs/heads/trunk b7e49b3ab -> 8e003d842 use max(current time from system clock, inProgress + 1) as CAS ballot patch by jbellis; reviewed by slebresne for CASSANDRA-5667 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/

[jira] [Resolved] (CASSANDRA-5667) Change timestamps used in CAS ballot proposals to be more resilient to clock skew

[ https://issues.apache.org/jira/browse/CASSANDRA-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-5667. --- Resolution: Fixed committed > Change timestamps used in CAS ball

[jira] [Updated] (CASSANDRA-5724) Timeouts for slice/rangeslice queries while some nodes versions are lower than 1.2 and some higher.

[ https://issues.apache.org/jira/browse/CASSANDRA-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5724: -- Assignee: Ryan McGuire Can we reproduce? There is already code to special case "ne

[jira] [Commented] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

[ https://issues.apache.org/jira/browse/CASSANDRA-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700221#comment-13700221 ] Sergio Bossa commented on CASSANDRA-5725: - bq. Here's how it's supposed to wor

[jira] [Commented] (CASSANDRA-5619) CAS UPDATE for a lost race: save round trip by returning column values

[ https://issues.apache.org/jira/browse/CASSANDRA-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700225#comment-13700225 ] Jonathan Ellis commented on CASSANDRA-5619: --- How does adding a boolean help

[jira] [Comment Edited] (CASSANDRA-5715) CAS on 'primary key only' table

[ https://issues.apache.org/jira/browse/CASSANDRA-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700240#comment-13700240 ] Jonathan Ellis edited comment on CASSANDRA-5715 at 7/4/13 5:26 PM: -

[jira] [Commented] (CASSANDRA-5715) CAS on 'primary key only' table

[ https://issues.apache.org/jira/browse/CASSANDRA-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700240#comment-13700240 ] Jonathan Ellis commented on CASSANDRA-5715: --- I guess we could restrict it to

[jira] [Commented] (CASSANDRA-5725) Silently failing messages in case of schema not fully propagated

[ https://issues.apache.org/jira/browse/CASSANDRA-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700246#comment-13700246 ] Jonathan Ellis commented on CASSANDRA-5725: --- IMO the fix here is to special

[jira] [Commented] (CASSANDRA-4131) Integrate Hive support to be in core cassandra

[ https://issues.apache.org/jira/browse/CASSANDRA-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700294#comment-13700294 ] Rohit Rai commented on CASSANDRA-4131: -- Actually, Hive support internally uses th

[jira] [Updated] (CASSANDRA-5697) cqlsh doesn't allow semicolons in BATCH statements

[ https://issues.apache.org/jira/browse/CASSANDRA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-5697: - Attachment: 5697.txt > cqlsh doesn't allow semicolons in BATCH statements

[jira] [Updated] (CASSANDRA-5534) Writing wide row causes high CPU usage after compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Zarutin updated CASSANDRA-5534: Tester: alexzar (was: enigmacurry) > Writing wide row causes high CPU usage after

[jira] [Commented] (CASSANDRA-5534) Writing wide row causes high CPU usage after compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700424#comment-13700424 ] Alex Zarutin commented on CASSANDRA-5534: - latest test on cassandra-1.2: $> c