Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1707787199.1247643794875.JavaMail.jira@brutus>
Date: Wed, 15 Jul 2009 00:43:14 -0700 (PDT)
From: "Evan Weaver (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-296) remove CQL
In-Reply-To: <338022631.1247607674877.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731323#action_12731323 ] 

Evan Weaver commented on CASSANDRA-296:
---------------------------------------

I don't care about cql specifically, but I want to make sure that the schema reflection tools are maintained, which I believe are related.

> remove CQL
> ----------
>
>                 Key: CASSANDRA-296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-296
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>
> I don't see a way to support binary column names in CQL once CASSANDRA-185 and CASSANDRA-240 are done.  You could do awful things like JDBC does for blob support but for the CLI that seems like the cure is worse than the disease.
> The obvious solution to me is to get rid of CQL.
> (This conflicts with CASSANDRA-289 -- we do want _some_ way to query the db from the cli.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.