DataStax Support Forums » Tag: cql3

DataStax Support Forums » Tag: cql3 - Recent Posts http://www.datastax.com/support-forums/tags/cql3 Software, Support, and Training for Apache Cassandra en-US Sat, 25 May 2013 05:44:28 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php xedin on "cql 3 support" http://www.datastax.com/support-forums/topic/cql-3-support#post-2692 Wed, 04 Jul 2012 09:50:34 +0000 xedin 2692@http://www.datastax.com/support-forums/ I think that it would be late July. Abhijit on "cql 3 support" http://www.datastax.com/support-forums/topic/cql-3-support#post-2680 Wed, 04 Jul 2012 03:21:34 +0000 Abhijit 2680@http://www.datastax.com/support-forums/ OK xedin. May i know when DSE 2.2 is going to be released? xedin on "cql 3 support" http://www.datastax.com/support-forums/topic/cql-3-support#post-2619 Tue, 03 Jul 2012 10:00:39 +0000 xedin 2619@http://www.datastax.com/support-forums/ It's planned for DSE 2.2 release. Abhijit on "cql 3 support" http://www.datastax.com/support-forums/topic/cql-3-support#post-2611 Tue, 03 Jul 2012 05:10:52 +0000 Abhijit 2611@http://www.datastax.com/support-forums/ when datastax enterprise is going to support cql 3 or cassandra 1.1+? Any news.... Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2169 Thu, 14 Jun 2012 08:18:01 +0000 Anonymous 2169@http://www.datastax.com/support-forums/ Thanks every one for the reply! And, Thepaul, Exactly that is the place where I got the answer, If, you want to use CQL 3.0 using JDBC driver, while creating connection you have to add a few words, connection = DriverManager.getConnection("jdbc:cassandra://localhost:9160/trial?version=3.0.0"); I mean, you have to specify the version name there. Thanks every one again!! thepaul on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2155 Wed, 13 Jun 2012 15:38:34 +0000 thepaul 2155@http://www.datastax.com/support-forums/ I wouldn't say cql 3 is still experimental. It's not even beta anymore. It ought to be as stable, or more, than cql 2 at this point. Version 1.1.0 of the JDBC driver (still in development) will support cql 3: see <a href="http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?spec=svn611a4f8def98d231d5aa80468c1e729a91f9259f&name=trunk&r=34afe6507c945ecc17fe0c2db68c1715f83af0f0" rel="nofollow">http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?spec=svn611a4f8def98d231d5aa80468c1e729a91f9259f&name=trunk&r=34afe6507c945ecc17fe0c2db68c1715f83af0f0</a> . So if you really need it, try the v1.1.0 branch of cassandra-jdbc. The python driver supports cql 3 now, if that helps. Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2138 Wed, 13 Jun 2012 10:20:17 +0000 Anonymous 2138@http://www.datastax.com/support-forums/ I don't believe that you can do that in current situation when CQL3 is still being experimental, the only way I know to run cql3 is to run cqlsh from C* bin directory with --cql3 flag. Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2131 Wed, 13 Jun 2012 03:45:48 +0000 Anonymous 2131@http://www.datastax.com/support-forums/ I am new to cassandra. As, I read many posts, most of them prescribe CQL 3.0. As I am a Java developer, I was trying cassandra using JDBC driver and Hector( using cql queries) to connect to database. But, I don't know how to upgrade those to CQL 3, and CQL 3 queries are not accepted by these frameworks. So, can somebody help me out of it with some examples. Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2025 Sun, 03 Jun 2012 20:13:00 +0000 Anonymous 2025@http://www.datastax.com/support-forums/ No, it wouldn't hurt anything, only this you would have to do to work with columns that are not in metadata is to use Thrift or CQL2. Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2024 Sun, 03 Jun 2012 18:31:04 +0000 Anonymous 2024@http://www.datastax.com/support-forums/ I just started with Cassandra a few weeks ago. One of the things I really like about it is the ability to add columns on the fly. Is it a valid assertion that 'dynamic' tables do not exist in cql 3.0? If I modify my code to catch the exception (unidentified column, or whatever it's called) and alter the columnfamily during insertion, is that sufficient? Put another way, if I end up with a columnfamily with a thousand columns defined in meta-data, but only a dozen used on each table, will that 'hurt' things? ---greg thepaul on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-1925 Wed, 16 May 2012 16:40:26 +0000 thepaul 1925@http://www.datastax.com/support-forums/ Yes, CQL 3 expects all columns to be defined in the metadata. What you should do about this depends on why you want col1 to exist. If it's the only extra column, then naturally you just need to add it to the metadata (something like <code>alter table mytab add col1 text;</code>. But note that CQL 3 rows are not necessarily the same as the underlying Cassandra rows ("storage engine rows"). So if your col1 is meant to be an example of a whole other set of ordered arbitrary column names and values that you'll be inserting, the right way to represent that in CQL might be to have a parallel table of "attributes" (or whatever): Example: <pre><code>CREATE TABLE mytab_attrs ( key text, attribute_name text, attribute_value text, PRIMARY KEY (key, attribute_name) ) WITH COMPACT STORAGE; INSERT INTO mytab (key, full_name, email) VALUES ('key1', 'Person 1', 'person1@gmail.com'); INSERT INTO mytab_attrs (key, attribute_name, attribute_value) VALUES ('key1', 'col1', 'value1');</code></pre> Anonymous on "Flexible schema in CQL 3" http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-1917 Tue, 15 May 2012 21:54:54 +0000 Anonymous 1917@http://www.datastax.com/support-forums/ We have a column family which has a few defined columns, and the rest are set at runtime. e.g. <pre><code>create column family mytab WITH comparator = UTF8Type AND key_validation_class=UTF8Type AND default_validation_class = UTF8Type AND column_metadata = [ {column_name: full_name, validation_class: UTF8Type} {column_name: email, validation_class: UTF8Type} {column_name: state, validation_class: UTF8Type} {column_name: gender, validation_class: UTF8Type} {column_name: birth_year, validation_class: LongType} ]; set mytab['key1']['full_name']='Person 1'; set mytab['key1']['email']='person1@gmail.com'; set mytab['key1']['col1']='value1';</code></pre> As you can see, the 3rd insert creates a new column 'col1' (which is not defined in the column_metadata). Now doing <code>list mytab</code> from cassandra-cli, shows the extra column <pre><code>[default@keyspace01] list mytab; Using default limit of 100 ------------------- RowKey: key1 => (column=col1, value=76616c756531, timestamp=1337108844540000) => (column=email, value=person1@gmail.com, timestamp=1337108716202000) => (column=full_name, value=Person 1, timestamp=1337108708791000)</code></pre> Same goes for CQL 2.0 <pre><code>cqlsh:keyspace01> select * from mytab; KEY,key1 | col1,76616c756531 | email,person1@gmail.com | full_name,Person 1</code></pre> But I can't see 'col1' if using CQL 3.0 <pre><code>$./cqlsh -3 cass01 Connected to OG Cluster at cass01:9160. [cqlsh 2.2.0 | Cassandra 1.1.0 | CQL spec 3.0.0 | Thrift protocol 19.30.0] Use HELP for help. cqlsh> use keyspace01; cqlsh:keyspace01> select * from mytab; key | birth_year | email | full_name | gender | state ------+------------+-------------------+-----------+--------+------- key | null | null | null | null | null key1 | null | <a href="mailto:person1@gmail.com">person1@gmail.com</a> | Person 1 | null | null</code></pre> Is this the intended behavior in CQL 3.0. coz having this flexibility is very important to us, which means we can't use CQL 3.0