cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8262) parse_for_table_meta errors out on queries with undefined grammars
Date Wed, 05 Nov 2014 22:48:33 GMT


Philip Thompson commented on CASSANDRA-8262:

/cc [~mishail] [~thobbs]

In 2.1.0, if a cqlsh query returned 0 rows, all that is printed is {{(0 rows)}}. After CASSANDRA-6910,
it also prints out the table metadata. If table metadata cannot be determined, is it acceptable
to just fall back to the 2.1.0 output, or would you also like a warning message that says
table metadata could not be determined?

> parse_for_table_meta errors out on queries with undefined grammars
> ------------------------------------------------------------------
>                 Key: CASSANDRA-8262
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Philip Thompson
>              Labels: cqlsh
>             Fix For: 2.1.2
>         Attachments: cassandra-2.1-8262-1.txt
> CASSANDRA-6910 introduced changes to the cqlsh function {{parse_for_table_meta}} that
cause an error to be thrown whenever a query does not have its grammar defined in
However, this is affecting queries that are legitimate cql syntax and are accepted by Cassandra,
but aren't defined in cqlsh. 

This message was sent by Atlassian JIRA

View raw message