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/07/14 23:41:14 UTC
[jira] Created: (CASSANDRA-296) remove CQL
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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741359#action_12741359 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
still getting errors. tried manually in case i was confusing jira-am somehow:
$ git-apply -p1 < v2-0001-CASSANDRA-296-fix-grammar-breakage.txt
error: patch failed: src/java/org/apache/cassandra/cli/Cli.g:85
error: src/java/org/apache/cassandra/cli/Cli.g: patch does not apply
> 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, 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.
[jira] Updated: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-296:
---------------------------------
Attachment: v1-0001-CASSANDRA-296-updated-CLI-output-for-README.txt.txt
> 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.
[jira] Updated: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-296:
---------------------------------
Attachment: v1-0003-CASSANDRA-296-remove-CQL.txt
v1-0002-CASSANDRA-296-remove-CQL-support-from-the-CLI.txt
v1-0001-CASSANDRA-296-fix-grammar-breakage.txt
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741378#action_12741378 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
yes, that was the problem.
+1
do you want updating README to be part of this ticket or another?
> 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, 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.
[jira] Updated: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-296:
-------------------------------------
Fix Version/s: 0.4
> 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
>
>
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731422#action_12731422 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
they're only related in that there is a cql statement to query it.
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741370#action_12741370 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
oops, I just noticed that the am from last night had completed part way and committed the first patch locally. that's probably the problem, I will retry.
> 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, 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731157#action_12731157 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
> isn't it /most/ likely that the byte[]s are UTF-8 and we can optimize for that case?
definitely not -- what are currently time sorted columns are going to become columns with either Long or UUID names.
> 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.
[jira] Assigned: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans reassigned CASSANDRA-296:
------------------------------------
Assignee: Eric Evans
> 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
>
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731166#action_12731166 ]
Michael Greene commented on CASSANDRA-296:
------------------------------------------
If keys need to be Comparable, can't they be Representable or something so we can map string<->byte for the keys? A parse() and format() or something?
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732715#action_12732715 ]
Eric Evans commented on CASSANDRA-296:
--------------------------------------
See http://markmail.org/thread/sqecvc7tyqptqqy2 for further discussion that took place on the cassandra-dev mailing list.
> 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
>
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Evan Weaver (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741496#action_12741496 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
+1
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731176#action_12731176 ]
Jonathan Ellis commented on CASSANDRA-296:
------------------------------------------
sure, if you (a) code it up AND (b) make the cql parser smart enough to figure out which it needs to use for a given column
(b) is going to be a bitch I think, which is why I am not volunteering :)
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (CASSANDRA-296) remove CQL
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-296:
----------------------------------------
Assignee: (was: Eric Evans)
> 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.
[jira] Updated: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-296:
---------------------------------
Attachment: v2-0003-CASSANDRA-296-remove-CQL.txt
v2-0002-CASSANDRA-296-remove-CQL-support-from-the-CLI.txt
v2-0001-CASSANDRA-296-fix-grammar-breakage.txt
> 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, 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741492#action_12741492 ]
Eric Evans commented on CASSANDRA-296:
--------------------------------------
v1-0001-CASSANDRA-296-updated-CLI-output-for-README.txt.txt is a stand-alone patch that updates README.txt
> 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.
[jira] Commented: (CASSANDRA-296) remove CQL
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741344#action_12741344 ]
Eric Evans commented on CASSANDRA-296:
--------------------------------------
rebased.
> 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, 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.