[jira] [Commented] (CASSANDRA-9984) Improve error reporting for malformed schemas in stress profile

["Jim Witschey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033870#comment-15033870 ] 

Jim Witschey commented on CASSANDRA-9984:
-----------------------------------------

The error message is much better, and I don't see any test failures resulting from this change:

http://cassci.datastax.com/view/Dev/view/tjake/job/tjake-9984-dtest/lastCompletedBuild/testReport/
http://cassci.datastax.com/view/Dev/view/tjake/job/tjake-9984-testall/1/

I'm +1.

> Improve error reporting for malformed schemas in stress profile
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-9984
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9984
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jim Witschey
>            Assignee: T Jake Luciani
>            Priority: Trivial
>             Fix For: 3.0.1, 3.1
>
>
> See this gist:
> https://gist.github.com/mambocab/a78fae8c356223245c63
> for an example of a profile that triggers the bug when used as a stress profile on trunk. It contains a number of old, now unused, configuration options in the table schema. The error raised when this schema is executed isn't propagated because of improper error handling.
> To reproduce this error with CCM you can save the file in the gist above as {{8-columns.yaml}} and run
> {code}
> ccm create -v git:trunk reproduce-error -n 1
> ccm start --wait-for-binary-proto
> ccm stress user profile=8-columns.yaml ops\(insert=1\) n=5K
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)