[
https://issues.apache.org/jira/browse/CASSANDRA-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius updated CASSANDRA-3865:
------------------------------------
Attachment: 3865_better_cli_ex_handling.txt
3865_better_cli_ex_handling.txt
has better decimal parsing as before.
Also has better error messaging when the exception is NoViableAltException.
For some reason the code special cased that exception and returned the
non-useful "Command not found" message. I just removed the special casing and
now the message is useful.
If there is some case that someone knows about that the message "Command not
found" is useful, i can put it back in for that specific case, but i couldn't
see it.
against cassandra-1.1
> Cassandra-cli returns 'command not found' instead of syntax error
> -----------------------------------------------------------------
>
> Key: CASSANDRA-3865
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3865
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: DSE 1.0.5
> Reporter: Eric Lubow
> Assignee: Dave Brosius
> Priority: Trivial
> Labels: cassandra-cli
> Fix For: 1.1.2
>
> Attachments: 3865_better_cli_ex_handling.txt, parse_doubles_better.txt
>
>
> When creating a column family from the output of 'show schema' with an index,
> there is a trailing comma after "index_type: 0," The return from this is a
> 'command not found' This is misleading because the command is found, there
> is just a syntax error.
> 'Command not found: `create column family $cfname ...`
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
