[jira] [Commented] (CASSANDRA-4511) Secondary index support for CQL3 collections
[ https://issues.apache.org/jira/browse/CASSANDRA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14200624#comment-14200624 ] Kristine Hahn commented on CASSANDRA-4511: -- Thanks, [~lexlythius]. http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/collection_type_r.html Secondary index support for CQL3 collections - Key: CASSANDRA-4511 URL: https://issues.apache.org/jira/browse/CASSANDRA-4511 Project: Cassandra Issue Type: Improvement Affects Versions: 1.2.0 beta 1 Reporter: Sylvain Lebresne Assignee: Sylvain Lebresne Fix For: 2.1 beta1 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-7853) select . . . in . . . order by regression
Kristine Hahn created CASSANDRA-7853:
Summary: select . . . in . . . order by regression
Key: CASSANDRA-7853
URL: https://issues.apache.org/jira/browse/CASSANDRA-7853
Project: Cassandra
Issue Type: Bug
Environment: MAC OSX cqlsh 3.1.8 (DSE 3.2.7) vs cqlsh 5.0.1 (Cassandra
2.1rc6)
Reporter: Kristine Hahn
Select statement that sorted results in earlier version gives an error in
Cassandra 2.1rc6. To reproduce problem:
{noformat}
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0-rc6-SNAPSHOT | CQL spec 3.2.0 | Native protocol
v3]
. . .
cqlsh:test CREATE TABLE emp (
... empID int,
... deptID int,
... first_name varchar,
... last_name varchar,
... PRIMARY KEY (empID, deptID));
cqlsh:test INSERT INTO emp (empID, deptID, first_name, last_name) VALUES (104,
15, 'jane', 'smith');
cqlsh:test INSERT INTO emp (empID, deptID, first_name, last_name) VALUES (130,
15, 'sughit', 'singh');
SELECT * FROM emp WHERE empID IN (130,104) ORDER BY deptID DESC;
code=2200 [Invalid query] message=Cannot page queries with both ORDER BY and a
IN restriction on the partition key; you must either remove the ORDER BY or the
IN and sort client side, or disable paging for this query
{noformat}
Using an earlier version:
{noformat}
Kris-Hahns-MacBook-Pro:bin krishahn$ ./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 3.1.8 | Cassandra 1.2.17.2 | CQL spec 3.0.0 | Thrift protocol 19.36.2]
. . .
cqlsh:excelsior CREATE TABLE emp4 (
... emp int,
... dept int,
... first_name varchar,
... last_name varchar,
... PRIMARY KEY (emp, dept));
cqlsh:excelsior INSERT INTO emp4 (emp, dept, first_name, last_name) VALUES
(104, 15, 'jane', 'smith');
cqlsh:excelsior INSERT INTO emp4 (emp, dept, first_name, last_name) VALUES
(130, 15, 'sughit', 'singh');
cqlsh:excelsior SELECT * FROM emp4 WHERE emp IN (130,104) ORDER BY dept DESC;
emp | dept | first_name | last_name
-+--++---
104 | 15 | jane | smith
130 | 15 | sughit | singh
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-7853) select . . . in . . . order by regression
[
https://issues.apache.org/jira/browse/CASSANDRA-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-7853:
-
Reproduced In: 2.1 rc6
select . . . in . . . order by regression
-
Key: CASSANDRA-7853
URL: https://issues.apache.org/jira/browse/CASSANDRA-7853
Project: Cassandra
Issue Type: Bug
Environment: MAC OSX cqlsh 3.1.8 (DSE 3.2.7) vs cqlsh 5.0.1
(Cassandra 2.1rc6)
Reporter: Kristine Hahn
Select statement that sorted results in earlier version gives an error in
Cassandra 2.1rc6. To reproduce problem:
{noformat}
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0-rc6-SNAPSHOT | CQL spec 3.2.0 | Native
protocol v3]
. . .
cqlsh:test CREATE TABLE emp (
... empID int,
... deptID int,
... first_name varchar,
... last_name varchar,
... PRIMARY KEY (empID, deptID));
cqlsh:test INSERT INTO emp (empID, deptID, first_name, last_name) VALUES
(104, 15, 'jane', 'smith');
cqlsh:test INSERT INTO emp (empID, deptID, first_name, last_name) VALUES
(130, 15, 'sughit', 'singh');
SELECT * FROM emp WHERE empID IN (130,104) ORDER BY deptID DESC;
code=2200 [Invalid query] message=Cannot page queries with both ORDER BY and
a IN restriction on the partition key; you must either remove the ORDER BY or
the IN and sort client side, or disable paging for this query
{noformat}
Using an earlier version:
{noformat}
Kris-Hahns-MacBook-Pro:bin krishahn$ ./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 3.1.8 | Cassandra 1.2.17.2 | CQL spec 3.0.0 | Thrift protocol 19.36.2]
. . .
cqlsh:excelsior CREATE TABLE emp4 (
... emp int,
... dept int,
... first_name varchar,
... last_name varchar,
... PRIMARY KEY (emp, dept));
cqlsh:excelsior INSERT INTO emp4 (emp, dept, first_name, last_name) VALUES
(104, 15, 'jane', 'smith');
cqlsh:excelsior INSERT INTO emp4 (emp, dept, first_name, last_name) VALUES
(130, 15, 'sughit', 'singh');
cqlsh:excelsior SELECT * FROM emp4 WHERE emp IN (130,104) ORDER BY dept DESC;
emp | dept | first_name | last_name
-+--++---
104 | 15 | jane | smith
130 | 15 | sughit | singh
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-7225) cqlsh help for CQL3 is often incorrect and should be modernized
[ https://issues.apache.org/jira/browse/CASSANDRA-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn updated CASSANDRA-7225: - Attachment: EXPAND.pdf Uploaded EXPAND statement to address [Tyler's comment|https://issues.apache.org/jira/browse/CASSANDRA-7225?focusedCommentId=14087861page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14087861]. cqlsh help for CQL3 is often incorrect and should be modernized --- Key: CASSANDRA-7225 URL: https://issues.apache.org/jira/browse/CASSANDRA-7225 Project: Cassandra Issue Type: Bug Components: Documentation website, Tools Reporter: Robert Stupp Assignee: Robert Stupp Priority: Trivial Labels: cql Attachments: 7225-cqlhelp.txt, EXPAND.pdf Just a small line of text in cqlsh help command indicates that is = and is = in CQL. This is confusing to many people (including me :) ) because I did not expect to return the equals portion. Please allow distinct behaviours for , =, and = in CQL queries. Maybe in combination with CASSANDRA-5184 and/or CASSANDRA-4914 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CASSANDRA-7225) cqlsh help for CQL3 is often incorrect and should be modernized
[ https://issues.apache.org/jira/browse/CASSANDRA-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14088303#comment-14088303 ] Kristine Hahn edited comment on CASSANDRA-7225 at 8/6/14 9:35 PM: -- Uploaded EXPAND statement (see attached PDF) to address [Tyler's comment|https://issues.apache.org/jira/browse/CASSANDRA-7225?focusedCommentId=14087861page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14087861]. was (Author: khahn): Uploaded EXPAND statement to address [Tyler's comment|https://issues.apache.org/jira/browse/CASSANDRA-7225?focusedCommentId=14087861page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14087861]. cqlsh help for CQL3 is often incorrect and should be modernized --- Key: CASSANDRA-7225 URL: https://issues.apache.org/jira/browse/CASSANDRA-7225 Project: Cassandra Issue Type: Bug Components: Documentation website, Tools Reporter: Robert Stupp Assignee: Robert Stupp Priority: Trivial Labels: cql Attachments: 7225-cqlhelp.txt, EXPAND.pdf Just a small line of text in cqlsh help command indicates that is = and is = in CQL. This is confusing to many people (including me :) ) because I did not expect to return the equals portion. Please allow distinct behaviours for , =, and = in CQL queries. Maybe in combination with CASSANDRA-5184 and/or CASSANDRA-4914 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CASSANDRA-7611) incomplete CREATE/DROP USER help and tab completion
Kristine Hahn created CASSANDRA-7611: Summary: incomplete CREATE/DROP USER help and tab completion Key: CASSANDRA-7611 URL: https://issues.apache.org/jira/browse/CASSANDRA-7611 Project: Cassandra Issue Type: Bug Components: Documentation website Reporter: Kristine Hahn Priority: Trivial IF NOT EXISTS/IF EXISTS doesn't appear in the online help and tab completion. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CASSANDRA-7527) Bump CQL version and update doc for 2.1
[ https://issues.apache.org/jira/browse/CASSANDRA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070890#comment-14070890 ] Kristine Hahn edited comment on CASSANDRA-7527 at 7/23/14 4:51 PM: --- Hi Jack, It's my understanding that https://cassandra.apache.org/doc/cql3/CQL.html is the official CQL doc. The C* team calls it the spec. That doc is installed in textile format with Cassandra source in the docs/cql directory. But I don't find any links to that web page on the Apache Cassandra site - I don't know who updates that Apache site. Kris On Tue, Jul 22, 2014 at 1:08 PM, Jack Krupansky (JIRA) j...@apache.org wrote: was (Author: khahn): Hi Jack, It's my understanding that https://cassandra.apache.org/doc/cql3/CQL.html is the official CQL doc. The C* team calls it the spec. That doc is installed in textile format with Cassandra source in the docs/cql directory. But I don't find any links to that web page on the Apache Cassandra site - I don't know who updates that Apache site. I don't think DataStax has anything to do with it. I'd send criticisms to Jonathan. Maybe you could send criticisms to the Apache site webmaster, but I wouldn't say anything about the link to the Datastax doc (don't want anybody open source maniac removing it!) Yes, the 2.1 docs will be released when 2.1 is released (on July 28 I heard). Kris On Tue, Jul 22, 2014 at 1:08 PM, Jack Krupansky (JIRA) j...@apache.org wrote: Bump CQL version and update doc for 2.1 --- Key: CASSANDRA-7527 URL: https://issues.apache.org/jira/browse/CASSANDRA-7527 Project: Cassandra Issue Type: Bug Reporter: Sylvain Lebresne Assignee: Tyler Hobbs Fix For: 2.1.0 Attachments: 7527-v2.txt, 7527.txt It appears we forgot to bump the CQL version for new 2.1 features (UDT, tuple type, collection indexing), nor did we update the textile doc -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CASSANDRA-7587) sstablekeys does not work with default configuration
Kristine Hahn created CASSANDRA-7587:
Summary: sstablekeys does not work with default configuration
Key: CASSANDRA-7587
URL: https://issues.apache.org/jira/browse/CASSANDRA-7587
Project: Cassandra
Issue Type: Bug
Components: Tools
Reporter: Kristine Hahn
Priority: Minor
The directory I tried to use with the sstablekeys tool is
path/apache-cassandra-2.1.0-rc4/data/data/music/playlists-e80c033011bd11e49269bb45d4dd025b/music-playlists-ka-1-Data.db
Results of attempting to use the command:
{quote}
sstablekeys
path2.1rc4/apache-cassandra-2.1.0-rc4/data/data/music/playlists-e80c033011bd11e49269bb45d4dd025b/music-playlists-ka-1-Data.db
ERROR 16:54:57 Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: commitlog_directory is
missing and -Dcassandra.storagedir is not set
at
org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:447)
~[apache-cassandra-2.1.0-rc4.jar:2.1.0-rc4]
at
org.apache.cassandra.config.DatabaseDescriptor.clinit(DatabaseDescriptor.java:129)
~[apache-cassandra-2.1.0-rc4.jar:2.1.0-rc4]
at
org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:406)
~[apache-cassandra-2.1.0-rc4.jar:2.1.0-rc4]
commitlog_directory is missing and -Dcassandra.storagedir is not set
Fatal configuration error; unable to start. See log for stacktrace.
{quote}
The system log says:
{quote}
ERROR [main] 2014-07-22 09:27:26,145 CassandraDaemon.java:203 - Directory
./../data/data doesn't exist
ERROR [main] 2014-07-22 09:27:26,154 CassandraDaemon.java:203 - Directory
./../data/commitlog doesn't exist
ERROR [main] 2014-07-22 09:27:26,154 CassandraDaemon.java:203 - Directory
./../data/saved_caches doesn't exist
{quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CASSANDRA-7527) Bump CQL version and update doc for 2.1
[ https://issues.apache.org/jira/browse/CASSANDRA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070591#comment-14070591 ] Kristine Hahn commented on CASSANDRA-7527: -- @tyler, shouldn't the keyspacename dot be next to the table name (after ON), not next to the name of the index? CREATE CUSTOM INDEX IF NOT EXISTS index_name ON keyspace_name.table_name ( KEYS ( column_name ) ) (USING class_name) (WITH OPTIONS = map) The tab completion doesn't show that you can preface an index name with a keyspace name using the dot notation. Bump CQL version and update doc for 2.1 --- Key: CASSANDRA-7527 URL: https://issues.apache.org/jira/browse/CASSANDRA-7527 Project: Cassandra Issue Type: Bug Reporter: Sylvain Lebresne Assignee: Tyler Hobbs Fix For: 2.1.0 Attachments: 7527-v2.txt, 7527.txt It appears we forgot to bump the CQL version for new 2.1 features (UDT, tuple type, collection indexing), nor did we update the textile doc -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7527) Bump CQL version and update doc for 2.1
[ https://issues.apache.org/jira/browse/CASSANDRA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070890#comment-14070890 ] Kristine Hahn commented on CASSANDRA-7527: -- Hi Jack, It's my understanding that https://cassandra.apache.org/doc/cql3/CQL.html is the official CQL doc. The C* team calls it the spec. That doc is installed in textile format with Cassandra source in the docs/cql directory. But I don't find any links to that web page on the Apache Cassandra site - I don't know who updates that Apache site. I don't think DataStax has anything to do with it. I'd send criticisms to Jonathan. Maybe you could send criticisms to the Apache site webmaster, but I wouldn't say anything about the link to the Datastax doc (don't want anybody open source maniac removing it!) Yes, the 2.1 docs will be released when 2.1 is released (on July 28 I heard). Kris On Tue, Jul 22, 2014 at 1:08 PM, Jack Krupansky (JIRA) j...@apache.org wrote: Bump CQL version and update doc for 2.1 --- Key: CASSANDRA-7527 URL: https://issues.apache.org/jira/browse/CASSANDRA-7527 Project: Cassandra Issue Type: Bug Reporter: Sylvain Lebresne Assignee: Tyler Hobbs Fix For: 2.1.0 Attachments: 7527-v2.txt, 7527.txt It appears we forgot to bump the CQL version for new 2.1 features (UDT, tuple type, collection indexing), nor did we update the textile doc -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7527) Bump CQL version and update doc for 2.1
[
https://issues.apache.org/jira/browse/CASSANDRA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067627#comment-14067627
]
Kristine Hahn commented on CASSANDRA-7527:
--
Is keyspacename misplaced here?
{quote}
-bc(syntax). create-index-stmt ::= CREATE ( CUSTOM )? INDEX ( IF NOT EXISTS
)? ( ( keyspacename '.' )? indexname )?
. . .
{quote}
Bump CQL version and update doc for 2.1
---
Key: CASSANDRA-7527
URL: https://issues.apache.org/jira/browse/CASSANDRA-7527
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Assignee: Tyler Hobbs
Fix For: 2.1.0
Attachments: 7527-v2.txt, 7527.txt
It appears we forgot to bump the CQL version for new 2.1 features (UDT, tuple
type, collection indexing), nor did we update the textile doc
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CASSANDRA-6642) line 297 of CQL.textile needs updated
Kristine Hahn created CASSANDRA-6642:
Summary: line 297 of CQL.textile needs updated
Key: CASSANDRA-6642
URL: https://issues.apache.org/jira/browse/CASSANDRA-6642
Project: Cassandra
Issue Type: Bug
Components: Documentation website
Environment: [CQL 3.1.4 doc,
cassandra-trunk|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
Reporter: Kristine Hahn
Priority: Minor
The behavior changed in 1.2.6.1 or earlier, but [the
doc|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
still says:
{quote}
The restriction for table with COMPACT STORAGE is that they support one and
only one column outside of the ones part of the PRIMARY KEY.
{quote}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CASSANDRA-6642) line 297 of CQL.textile needs updated
[
https://issues.apache.org/jira/browse/CASSANDRA-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-6642:
-
Description:
[the
doc|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
says:
{quote}
The restriction for table with COMPACT STORAGE is that they support one and
only one column outside of the ones part of the PRIMARY KEY.
{quote}
Shouldn't it say, ... outside of the ones that are part of a compound primary
key?
was:
The behavior changed in 1.2.6.1 or earlier, but [the
doc|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
still says:
{quote}
The restriction for table with COMPACT STORAGE is that they support one and
only one column outside of the ones part of the PRIMARY KEY.
{quote}
line 297 of CQL.textile needs updated
-
Key: CASSANDRA-6642
URL: https://issues.apache.org/jira/browse/CASSANDRA-6642
Project: Cassandra
Issue Type: Bug
Components: Documentation website
Environment: [CQL 3.1.4 doc,
cassandra-trunk|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
Reporter: Kristine Hahn
Priority: Minor
[the
doc|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#partition-key-and-clustering]
says:
{quote}
The restriction for table with COMPACT STORAGE is that they support one and
only one column outside of the ones part of the PRIMARY KEY.
{quote}
Shouldn't it say, ... outside of the ones that are part of a compound primary
key?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CASSANDRA-6627) nodetool help for handoff and truncatehints nits
Kristine Hahn created CASSANDRA-6627: Summary: nodetool help for handoff and truncatehints nits Key: CASSANDRA-6627 URL: https://issues.apache.org/jira/browse/CASSANDRA-6627 Project: Cassandra Issue Type: Bug Components: Documentation website Environment: 2.1 trunk Reporter: Kristine Hahn Priority: Trivial The description for disablehandoff is missing. It has the same description as disablegossip. At the end of the SYNOPSIS of truncatehints, the angle brackets are missing around endpoint. nodetool [(-h host | --host host)] [(-p port | --port port)] [(-pw password | --password password)] [(-u username | --username username)] truncatehints [--] [endpoint] -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CASSANDRA-6617) nodetool help removenode man page missing status, force, ID options description
Kristine Hahn created CASSANDRA-6617: Summary: nodetool help removenode man page missing status, force, ID options description Key: CASSANDRA-6617 URL: https://issues.apache.org/jira/browse/CASSANDRA-6617 Project: Cassandra Issue Type: Bug Components: Documentation website Environment: 2.1-SNAPSHOT Reporter: Kristine Hahn Priority: Trivial Man page OPTIONS section looks like you were interrupted before finishing the description: OPTIONS . . . status|force|ID The keyspace and column family name -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CASSANDRA-5132) unfriendly error message during create table map collection
Kristine Hahn created CASSANDRA-5132: Summary: unfriendly error message during create table map collection Key: CASSANDRA-5132 URL: https://issues.apache.org/jira/browse/CASSANDRA-5132 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.2.0 Environment: [cqlsh 2.3.0 | Cassandra 1.2.0-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol 19.35.0] Reporter: Kristine Hahn Priority: Trivial cqlsh:music create table test (id uuid PRIMARY KEY, testmap maptimestamp, nonsense); Bad Request: Failed parsing statement: [create table test (id uuid PRIMARY KEY, testmap maptimestamp, nonsense);] reason: NullPointerException null -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5117) CQL 3 ALTER TABLE ... ADD causes OOB
[
https://issues.apache.org/jira/browse/CASSANDRA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-5117:
-
Environment: Mac OSX, DS Java Driver, apache-cassandra-1.2.0-src downloaded
from project Jan 2, 2013 (was: Mac OSX, apache-cassandra-1.2.0-src downloaded
from project Jan 2, 2013)
CQL 3 ALTER TABLE ... ADD causes OOB
Key: CASSANDRA-5117
URL: https://issues.apache.org/jira/browse/CASSANDRA-5117
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0
Environment: Mac OSX, DS Java Driver, apache-cassandra-1.2.0-src
downloaded from project Jan 2, 2013
Reporter: Kristine Hahn
Attachments: OOB.txt
To reproduce:
./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol
19.35.0]
Use HELP for help.
cqlsh create keyspace music with replication = {'CLASS' :
... 'SimpleStrategy', 'replication_factor' : 3};
cqlsh use music
... ;
cqlsh:music CREATE TABLE songs (
... id uuid PRIMARY KEY,
... title text,
... album text,
... artist text,
... data blob
... );
cqlsh:music insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres
Hombres');
cqlsh:music insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
cqlsh:music insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
cqlsh:music CREATE TABLE song_tags (
... id uuid,
... tag_name text,
... PRIMARY KEY (id, tag_name)
... );
cqlsh:music select * from song_tags;
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'blues');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', 'covers');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '1973');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', '2007');
cqlsh:music select * from song_tags;
id | tag_name
--+--
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 |blues
8a172618-b121-4136-bb10-f665cfc469eb | 2007
8a172618-b121-4136-bb10-f665cfc469eb | covers
cqlsh:music drop table song_tags;
cqlsh:music ALTER TABLE songs ADD tags settext;
TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5117) CQL 3 ALTER TABLE ... ADD causes NPE
Kristine Hahn created CASSANDRA-5117:
Summary: CQL 3 ALTER TABLE ... ADD causes NPE
Key: CASSANDRA-5117
URL: https://issues.apache.org/jira/browse/CASSANDRA-5117
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0
Environment: Mac OSX, apache-cassandra-1.2.0-src downloaded from
project Jan 2, 2013
Reporter: Kristine Hahn
To reproduce:
./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol
19.35.0]
Use HELP for help.
cqlsh create keyspace music with replication = {'CLASS' :
... 'SimpleStrategy', 'replication_factor' : 3};
cqlsh use music
... ;
cqlsh:music CREATE TABLE songs (
... id uuid PRIMARY KEY,
... title text,
... album text,
... artist text,
... data blob
... );
cqlsh:music insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres Hombres');
cqlsh:music insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
cqlsh:music insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
cqlsh:music CREATE TABLE song_tags (
... id uuid,
... tag_name text,
... PRIMARY KEY (id, tag_name)
... );
cqlsh:music select * from song_tags;
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'blues');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', 'covers');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '1973');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', '2007');
cqlsh:music select * from song_tags;
id | tag_name
--+--
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 |blues
8a172618-b121-4136-bb10-f665cfc469eb | 2007
8a172618-b121-4136-bb10-f665cfc469eb | covers
cqlsh:music drop table song_tags;
cqlsh:music ALTER TABLE songs ADD tags settext;
TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5117) CQL 3 ALTER TABLE ... ADD causes OOB
[
https://issues.apache.org/jira/browse/CASSANDRA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-5117:
-
Summary: CQL 3 ALTER TABLE ... ADD causes OOB (was: CQL 3 ALTER TABLE ...
ADD causes NPE)
CQL 3 ALTER TABLE ... ADD causes OOB
Key: CASSANDRA-5117
URL: https://issues.apache.org/jira/browse/CASSANDRA-5117
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0
Environment: Mac OSX, apache-cassandra-1.2.0-src downloaded from
project Jan 2, 2013
Reporter: Kristine Hahn
To reproduce:
./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol
19.35.0]
Use HELP for help.
cqlsh create keyspace music with replication = {'CLASS' :
... 'SimpleStrategy', 'replication_factor' : 3};
cqlsh use music
... ;
cqlsh:music CREATE TABLE songs (
... id uuid PRIMARY KEY,
... title text,
... album text,
... artist text,
... data blob
... );
cqlsh:music insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres
Hombres');
cqlsh:music insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
cqlsh:music insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
cqlsh:music CREATE TABLE song_tags (
... id uuid,
... tag_name text,
... PRIMARY KEY (id, tag_name)
... );
cqlsh:music select * from song_tags;
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'blues');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', 'covers');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '1973');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', '2007');
cqlsh:music select * from song_tags;
id | tag_name
--+--
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 |blues
8a172618-b121-4136-bb10-f665cfc469eb | 2007
8a172618-b121-4136-bb10-f665cfc469eb | covers
cqlsh:music drop table song_tags;
cqlsh:music ALTER TABLE songs ADD tags settext;
TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5117) CQL 3 ALTER TABLE ... ADD causes OOB
[
https://issues.apache.org/jira/browse/CASSANDRA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-5117:
-
Attachment: OOB.txt
system.log
CQL 3 ALTER TABLE ... ADD causes OOB
Key: CASSANDRA-5117
URL: https://issues.apache.org/jira/browse/CASSANDRA-5117
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0
Environment: Mac OSX, apache-cassandra-1.2.0-src downloaded from
project Jan 2, 2013
Reporter: Kristine Hahn
Attachments: OOB.txt
To reproduce:
./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol
19.35.0]
Use HELP for help.
cqlsh create keyspace music with replication = {'CLASS' :
... 'SimpleStrategy', 'replication_factor' : 3};
cqlsh use music
... ;
cqlsh:music CREATE TABLE songs (
... id uuid PRIMARY KEY,
... title text,
... album text,
... artist text,
... data blob
... );
cqlsh:music insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres
Hombres');
cqlsh:music insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
cqlsh:music insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
cqlsh:music CREATE TABLE song_tags (
... id uuid,
... tag_name text,
... PRIMARY KEY (id, tag_name)
... );
cqlsh:music select * from song_tags;
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'blues');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', 'covers');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '1973');
cqlsh:music INSERT INTO song_tags (id, tag_name) VALUES
('8a172618-b121-4136-bb10-f665cfc469eb', '2007');
cqlsh:music select * from song_tags;
id | tag_name
--+--
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973
a3e64f8f-bd44-4f28-b8d9-6938726e34d4 |blues
8a172618-b121-4136-bb10-f665cfc469eb | 2007
8a172618-b121-4136-bb10-f665cfc469eb | covers
cqlsh:music drop table song_tags;
cqlsh:music ALTER TABLE songs ADD tags settext;
TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-5012:
-
Attachment: log.txt
Sorry for not including the log. Here it is if you're still interested in it.
alter table alter causes TSocket read 0 bytes
-
Key: CASSANDRA-5012
URL: https://issues.apache.org/jira/browse/CASSANDRA-5012
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0 beta 2
Environment: On Mac OSX ./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-rc1-SNAPSHOT | CQL spec 3.0.0 | Thrift
protocol 19.35.0]
Reporter: Kristine Hahn
Assignee: Sylvain Lebresne
Fix For: 1.2.0
Attachments: 5012.patch, log.txt
Altering the type of a clustering key column causes TSocket error.
To reproduce the problem:
1. CREATE SCHEMA Excalibur WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 3 };
2. CREATE TABLE Excalibur.Test ( id int, species text, color text, PRIMARY
KEY ((id, species), color)) WITH compaction = { 'class' :
'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
3. Alter table Excalibur.test ALTER color type int;
Expected result: Error message saying something like, Changing the type of a
clustering key is not allowed.
Actual result: TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes
Kristine Hahn created CASSANDRA-5012:
Summary: alter table alter causes TSocket read 0 bytes
Key: CASSANDRA-5012
URL: https://issues.apache.org/jira/browse/CASSANDRA-5012
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0 beta 2
Environment: On Mac OSX ./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-rc1-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol
19.35.0]
Reporter: Kristine Hahn
Altering the type of a clustering key column cause TSocket error.
To reproduce the problem:
1. CREATE SCHEMA Excalibur WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 3 };
2. CREATE TABLE Excalibur.Test ( id int, species text, color text, PRIMARY
KEY ((id, species), color)) WITH compaction = { 'class' :
'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
3. Alter table Excalibur.test ALTER color type int;
Expected result: Error message saying something like, Changing the type of a
clustering key is not allowed.
Actual result: TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes
[
https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-5012:
-
Description:
Altering the type of a clustering key column causes TSocket error.
To reproduce the problem:
1. CREATE SCHEMA Excalibur WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 3 };
2. CREATE TABLE Excalibur.Test ( id int, species text, color text, PRIMARY
KEY ((id, species), color)) WITH compaction = { 'class' :
'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
3. Alter table Excalibur.test ALTER color type int;
Expected result: Error message saying something like, Changing the type of a
clustering key is not allowed.
Actual result: TSocket read 0 bytes
was:
Altering the type of a clustering key column cause TSocket error.
To reproduce the problem:
1. CREATE SCHEMA Excalibur WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 3 };
2. CREATE TABLE Excalibur.Test ( id int, species text, color text, PRIMARY
KEY ((id, species), color)) WITH compaction = { 'class' :
'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
3. Alter table Excalibur.test ALTER color type int;
Expected result: Error message saying something like, Changing the type of a
clustering key is not allowed.
Actual result: TSocket read 0 bytes
alter table alter causes TSocket read 0 bytes
-
Key: CASSANDRA-5012
URL: https://issues.apache.org/jira/browse/CASSANDRA-5012
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0 beta 2
Environment: On Mac OSX ./cqlsh
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 1.2.0-rc1-SNAPSHOT | CQL spec 3.0.0 | Thrift
protocol 19.35.0]
Reporter: Kristine Hahn
Altering the type of a clustering key column causes TSocket error.
To reproduce the problem:
1. CREATE SCHEMA Excalibur WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 3 };
2. CREATE TABLE Excalibur.Test ( id int, species text, color text, PRIMARY
KEY ((id, species), color)) WITH compaction = { 'class' :
'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
3. Alter table Excalibur.test ALTER color type int;
Expected result: Error message saying something like, Changing the type of a
clustering key is not allowed.
Actual result: TSocket read 0 bytes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4999) CQL2 returns empty results from song_tags
[
https://issues.apache.org/jira/browse/CASSANDRA-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristine Hahn updated CASSANDRA-4999:
-
Summary: CQL2 returns empty results from song_tags (was: 1.2.0-beta2 does
returns empty results from song_tags in CQL2)
CQL2 returns empty results from song_tags
-
Key: CASSANDRA-4999
URL: https://issues.apache.org/jira/browse/CASSANDRA-4999
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.2.0 beta 2
Reporter: Kristine Hahn
Priority: Trivial
To reproduce the problem:
1. start CQL2 ./cqlsh --cql2
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 0.0.0 | CQL spec 2.0.0 | Thrift protocol 19.35.0]
2. create a keyspace and use it.
3. create the tables and insert data:
CREATE COLUMNFAMILY songs (id uuid PRIMARY KEY, title text, album text,
artist text, data blob);
CREATE COLUMNFAMILY song_tags (id uuid PRIMARY KEY) WITH comparator=text;
insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres
Hombres');
insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
insert into song_tags ('id', 'blues', '1973') values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '', '');
insert into song_tags ('id', 'covers', '2007') values
('8a172618-b121-4136-bb10-f665cfc469eb', '', '');
4. Select * from song_tags;
Expected result:
id,8a172618-b121-4136-bb10-f665cfc469eb | 2007, | covers,
id,a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973, | blues,
Actual result:
none
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4999) 1.2.0-beta2 does returns empty results from song_tags in CQL2
Kristine Hahn created CASSANDRA-4999:
Summary: 1.2.0-beta2 does returns empty results from song_tags in
CQL2
Key: CASSANDRA-4999
URL: https://issues.apache.org/jira/browse/CASSANDRA-4999
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.2.0 beta 2
Reporter: Kristine Hahn
Priority: Trivial
To reproduce the problem:
1. start CQL2 ./cqlsh --cql2
Connected to Test Cluster at localhost:9160.
[cqlsh 2.3.0 | Cassandra 0.0.0 | CQL spec 2.0.0 | Thrift protocol 19.35.0]
2. create a keyspace and use it.
3. create the tables and insert data:
CREATE COLUMNFAMILY songs (id uuid PRIMARY KEY, title text, album text, artist
text, data blob);
CREATE COLUMNFAMILY song_tags (id uuid PRIMARY KEY) WITH comparator=text;
insert into songs (id, title, artist, album) values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', 'La Grange', 'ZZ Top', 'Tres Hombres');
insert into songs (id, title, artist, album) values
('8a172618-b121-4136-bb10-f665cfc469eb', 'Moving in Stereo', 'Fu Manchu', 'We
Must Obey');
insert into songs (id, title, artist, album) values
('62c36092-82a1-3a00-93d1-46196ee77204', 'Outside Woman Blues', 'Back Door
Slam', 'Roll Away');
insert into song_tags ('id', 'blues', '1973') values
('a3e64f8f-bd44-4f28-b8d9-6938726e34d4', '', '');
insert into song_tags ('id', 'covers', '2007') values
('8a172618-b121-4136-bb10-f665cfc469eb', '', '');
4. Select * from song_tags;
Expected result:
id,8a172618-b121-4136-bb10-f665cfc469eb | 2007, | covers,
id,a3e64f8f-bd44-4f28-b8d9-6938726e34d4 | 1973, | blues,
Actual result:
none
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4879) CQL help in trunk/doc/cql3/CQL.textile outdated
Kristine Hahn created CASSANDRA-4879: Summary: CQL help in trunk/doc/cql3/CQL.textile outdated Key: CASSANDRA-4879 URL: https://issues.apache.org/jira/browse/CASSANDRA-4879 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 beta 1 Reporter: Kristine Hahn https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. It would be helpful to have all the changes (don't know what they are) included for updating the datastax.com docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4879) CQL help in trunk/doc/cql3/CQL.textile outdated
[ https://issues.apache.org/jira/browse/CASSANDRA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn updated CASSANDRA-4879: - Description: https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... doesn't completely explain optional like [] does, but any doubt could be erased by examples. was:https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. It would be helpful to have all the changes (don't know what they are) included for updating the datastax.com docs. CQL help in trunk/doc/cql3/CQL.textile outdated --- Key: CASSANDRA-4879 URL: https://issues.apache.org/jira/browse/CASSANDRA-4879 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 beta 1 Reporter: Kristine Hahn Assignee: Sylvain Lebresne Labels: documentation https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... doesn't completely explain optional like [] does, but any doubt could be erased by examples. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4879) CQL help in trunk/doc/cql3/CQL.textile outdated
[ https://issues.apache.org/jira/browse/CASSANDRA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn updated CASSANDRA-4879: - Description: https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... in italics doesn't strictly explain things like nested [...] does, but it's easier on the eyes and loosely understandable. Any doubt could be erased by examples, I think. was: https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... doesn't completely explain optional like [] does, but any doubt could be erased by examples. CQL help in trunk/doc/cql3/CQL.textile outdated --- Key: CASSANDRA-4879 URL: https://issues.apache.org/jira/browse/CASSANDRA-4879 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 beta 1 Reporter: Kristine Hahn Assignee: Sylvain Lebresne Labels: documentation https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... in italics doesn't strictly explain things like nested [...] does, but it's easier on the eyes and loosely understandable. Any doubt could be erased by examples, I think. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4879) CQL help in trunk/doc/cql3/CQL.textile outdated
[ https://issues.apache.org/jira/browse/CASSANDRA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristine Hahn updated CASSANDRA-4879: - Description: https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. Last time, I updated the CQL.textile for thePaul to review. Want me to do it again? BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... in italics doesn't strictly explain things like nested [...] does, but it's easier on the eyes and loosely understandable. Any doubt could be erased by examples, I think. http://website-staging.dev.datastax.com/docs/1.2/cql_cli/cql/ALTER_COLUMNFAMILY and other commands show proposed formatting but no collections stuff yet. (username riptano, password joB4aesi4e). Robin's thinks it's ok, what do you think? was: https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. I could update the CQL.textile, like last time, and would like to save Dev from doing it. I'm trying to get info from tickets, but not finding some things, like how you enter multiple DC values replication factors. No tab complete. BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... in italics doesn't strictly explain things like nested [...] does, but it's easier on the eyes and loosely understandable. Any doubt could be erased by examples, I think. CQL help in trunk/doc/cql3/CQL.textile outdated --- Key: CASSANDRA-4879 URL: https://issues.apache.org/jira/browse/CASSANDRA-4879 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 beta 1 Reporter: Kristine Hahn Assignee: Sylvain Lebresne Labels: documentation https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile doesn't include the new create keyspace syntax or the collections. Last time, I updated the CQL.textile for thePaul to review. Want me to do it again? BNR-like formatting needs to be replaced, right?, because the brackets now have literal meaning. In the datastax.com docs, I test-applied this custom formatting to commands and it seems ok: Uppercase means literal (lowercase nonliteral), italics mean optional, the | symbol means OR, ... means repeatable. The ... in italics doesn't strictly explain things like nested [...] does, but it's easier on the eyes and loosely understandable. Any doubt could be erased by examples, I think. http://website-staging.dev.datastax.com/docs/1.2/cql_cli/cql/ALTER_COLUMNFAMILY and other commands show proposed formatting but no collections stuff yet. (username riptano, password joB4aesi4e). Robin's thinks it's ok, what do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
