[
https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741845#action_12741845
]
Hudson commented on CASSANDRA-296:
----------------------------------
Integrated in Cassandra #164 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/164/])
updated CLI output for README.txt
remove CQL
remove CQL support from the CLI
fix grammar breakage
Changeset ada820 was an attempt to make hostname parsing less stupid,
(i.e. don't allow underscores; do allow hyphens; allow IP addresses).
It didn't entirely fix the problems it set out to and it broke
parsing of anything that used the "Identifier" lexer, (for example
the thrift {get,set} ... commands).
This changeset partially reverts ada820 until a proper fix to
hostname parsing can be found.
> 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-0001-CASSANDRA-296-updated-CLI-output-for-README.txt.txt,
> v1-0002-CASSANDRA-296-remove-CQL-support-from-the-CLI.txt,
> v1-0003-CASSANDRA-296-remove-CQL.txt,
> v2-0001-CASSANDRA-296-fix-grammar-breakage.txt,
> v2-0002-CASSANDRA-296-remove-CQL-support-from-the-CLI.txt,
> v2-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.
