You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/08/10 04:56:14 UTC
[jira] Commented: (CASSANDRA-296) remove CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741166#action_12741166 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
got error: src/java/org/apache/cassandra/cli/CliClient.java: patch does not apply
probably needs post-CASSANDRA-329 rebase, sorry
> remove CQL
> ----------
>
> Key: CASSANDRA-296
> URL: https://issues.apache.org/jira/browse/CASSANDRA-296
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Eric Evans
> Fix For: 0.4
>
> Attachments: v1-0001-CASSANDRA-296-fix-grammar-breakage.txt, v1-0002-CASSANDRA-296-remove-CQL-support-from-the-CLI.txt, v1-0003-CASSANDRA-296-remove-CQL.txt
>
>
> 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.