Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 24 Feb 2016 01:48:18 +0000 (UTC)
From: "Rafael Sanches (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12941605.1456278453000.129246.1456278498132@Atlassian.JIRA>
In-Reply-To: <JIRA.12941605.1456278453000@Atlassian.JIRA>
References: <JIRA.12941605.1456278453000@Atlassian.JIRA>
 <JIRA.12941605.1456278453367@arcas>
Subject: [jira] [Created] (CASSANDRA-11222) datanucleus-cassandra won't work
 with cassandra 3.0 system.* metadata.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rafael Sanches created CASSANDRA-11222:
------------------------------------------

             Summary: datanucleus-cassandra won't work with cassandra 3.0 system.* metadata.
                 Key: CASSANDRA-11222
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11222
             Project: Cassandra
          Issue Type: Wish
          Components: CQL
         Environment: Java JDO
            Reporter: Rafael Sanches
            Priority: Blocker
             Fix For: 3.0.x


Hi, 

I'm starting a new project and was hoping to upgrade directly to cassandra 3.0, so it would save us a migration from 2.2 later on. 

Unfortunately, the datanucleus-cassandra-5.0.0-m1 (latest) don't support the 3.0 data model. 

Errors like these will appear because of JDO:
https://issues.apache.org/jira/browse/CASSANDRA-10996

To be more specific, this class does things like:
StringBuilder stmtBuilder = new StringBuilder("SELECT keyspace_name FROM system.schema_keyspaces WHERE keyspace_name=?;");

https://github.com/datanucleus/datanucleus-cassandra/blob/master/src/main/java/org/datanucleus/store/cassandra/CassandraSchemaHandler.java

It doesn't seem like the Datanucleus guys are looking to fix this, since the last update on datanucleus-cassandra was on 2014. I will open an issue there too. Hope can reach contributors from both places. 

I guess opening an issue here is more a "heads up", because more developers will waste time on this soon.

thanks
rafa


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)