[
https://issues.apache.org/jira/browse/CASSANDRA-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282140#comment-13282140
]
Yuki Morishita commented on CASSANDRA-3865:
-------------------------------------------
That't one way to fix parsing problem, but in my understanding, what Eric is
saying is that it's hard to find the error from the message above.
If we can display more user friendly message like "Parse error:
read_repair_chance = .25", instead of saying "Command not found", user can
easily fix what's wrong.
I'm fine with current Double definition if we can fix the error message. What
do you think, Pavel?
> 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.0.11, 1.1.1
>
> Attachments: 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
