DataStax Support Forums » Tag: JDBC driver

DataStax Support Forums » Tag: JDBC driver - Recent Posts http://www.datastax.com/support-forums/tags/jdbc-driver Software, Support, and Training for Apache Cassandra en-US Thu, 23 May 2013 19:05:40 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php Mutatio on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-6165 Tue, 28 Aug 2012 10:54:18 +0000 Mutatio 6165@http://www.datastax.com/support-forums/ Oddly, my DataStax user account was purged. In regards to this problem, it's not non-existent with Cassandra 1.1.x from the Apache Debian repositories in conjunction with the latest Cassandra JDBC 1.1. It now works as expected. To above, use the version parameter in the connection string, like so: <code>jdbc:cassandra://127.0.0.1:9160/myKeyspace?version=3.0.0</code> 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 "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-2117 Tue, 12 Jun 2012 09:19:23 +0000 Anonymous 2117@http://www.datastax.com/support-forums/ How to use CQL 3.0 with JDBC driver. 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 Anonymous on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-1959 Tue, 22 May 2012 13:43:59 +0000 Anonymous 1959@http://www.datastax.com/support-forums/ Sorry for the lack of response, I'll look into this again in the next few days. I did notice when executing my build scripts that JDBC had a new 1.1 branch (I'm already using trunk), on first glance I assumed it was just created to align with the new stable Cassandra 1.1 release. The latest revision looks promising but then again POM/Build dependencies have been updated in line with 1.1* since March. 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 Anonymous on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-1810 Tue, 01 May 2012 17:29:02 +0000 Anonymous 1810@http://www.datastax.com/support-forums/ I'm seeing this issue as well with Cassandra 1.1. I tried inlining the values instead of using a PreparedStatement. That did work, but isn't a workable long-term solution. I'm using the latest JDBC source from the git repository. Any thoughts before I go additional digging? joaquin on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-1696 Wed, 18 Apr 2012 19:28:17 +0000 joaquin 1696@http://www.datastax.com/support-forums/ Also, could you try inlining the values for stmtInsertPost instead of setting them afterwards? What result does that give you? Thanks, Joaquin joaquin on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-1695 Wed, 18 Apr 2012 19:23:25 +0000 joaquin 1695@http://www.datastax.com/support-forums/ Hello, Perhaps you should try running this code from jdbc's trunk branch: <a href="http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/list?name=trunk" rel="nofollow">http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/list?name=trunk</a> There have been recent commits specifically for 1.1. Do let us know if this helps, Joaquin Anonymous on "Cassandra JDBC Error" http://www.datastax.com/support-forums/topic/cassandra-jdbc-error#post-1462 Thu, 29 Mar 2012 18:19:51 +0000 Anonymous 1462@http://www.datastax.com/support-forums/ Has anybody managed to get the Cassandra JDBC 1.0.5 to work with Cassandra 1.1+? Using these "schemas": <pre><code>CREATE KEYSPACE mutatio WITH strategy_class = 'SimpleStrategy' AND strategy_options:replication_factor = 1; USE mutatio; CREATE COLUMNFAMILY blogPosts ( id bigint PRIMARY KEY, userID int, title varchar, body text, created timestamp, edited timestamp );</code></pre> And query like so (connecting to Cassandra is fine): <pre><code>try { PreparedStatement stmtInsertPost = cassandra.prepareStatement("UPDATE blogPosts SET userID=?, title=?, body=?, created=?, edited=? WHERE id=?"); byte i = 0; stmtInsertPost.setInt(i++, post.userID); stmtInsertPost.setString(i++, post.title); stmtInsertPost.setString(i++, post.body); stmtInsertPost.setString(i++, post.created); stmtInsertPost.setString(i++, post.edited); stmtInsertPost.setLong(i++, post.id); stmtInsertPost.executeUpdate(); } catch (Exception ex) { writer.println(ex.toString()); }</code></pre> Example object: <pre><code>{ "id" : 2339993644662819568, "userID" : 1, "created" : "2012-03-29 19:15:46+0100", "edited" : "2012-03-29 19:15:46+0100", "body" : "Hello World!", "title" : "Test Blog Post", "tags" : [ "test", "testing" ] }</code></pre> I get a generic SQL exception in the Java application (I'm using Apache DBCP) and by running ./cassandra -f I can see this exception: <pre><code>ERROR 19:02:01,587 Error occurred during processing of message. java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:604) at java.util.ArrayList.get(ArrayList.java:382) at org.apache.cassandra.cql.Term.getByteBuffer(Term.java:99) at org.apache.cassandra.cql.UpdateStatement.prepareRowMutations(UpdateStatement.java:163) at org.apache.cassandra.cql.UpdateStatement.prepareRowMutations(UpdateStatement.java:127) at org.apache.cassandra.cql.QueryProcessor.batchUpdate(QueryProcessor.java:252) at org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:591) at org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:873) at org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1226) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3458) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3446) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:184) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)</code></pre> Has anybody experienced this and discovered a solution or is it simply a mismatch of edge build of Cassandra conflicting with the Cassandra-JDBC which doesn't seem to get updated all that often?