cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Greene (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-296) remove CQL
Date Tue, 14 Jul 2009 21:55:14 GMT

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

Michael Greene commented on CASSANDRA-296:
------------------------------------------

-1 for now.  HBase manages to use binary keys in their shell, I don't see how either of those
referenced issues explicitly prohibit CQL or the CLI.  HBASE-1363 and HBASE-1509 are relevant,
but even beyond the treatment of byte[] arrays, isn't it /most/ likely that the byte[]s are
UTF-8 and we can optimize for that case?

> remove CQL
> ----------
>
>                 Key: CASSANDRA-296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-296
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Eric Evans
>
> 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.


Mime
View raw message