cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2649) work-around schema disagreements from cqlsh
Date Fri, 20 May 2011 20:05:47 GMT

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

Jonathan Ellis commented on CASSANDRA-2649:
-------------------------------------------

bq. A better solution would probably be to compare schema versions

Agreed.  Why not just do that?  describe_schema_versions makes it extremely easy.

> work-around schema disagreements from cqlsh
> -------------------------------------------
>
>                 Key: CASSANDRA-2649
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2649
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.8.0 beta 2
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>              Labels: cql
>             Fix For: 0.8.0
>
>         Attachments: v1-0001-CASSANDRA-2649-try-to-work-around-schema-disagreement-.txt
>
>
> It is handy to be able to put CQL statements in a flat-file and load them by redirecting
to {{cqlsh}} stdin, but this can fail on a cluster when executing statements that modify schema.
> The attached patch works around this problem by retrying up to 3 times, with a progressive
delay after each attempt.  A better solution would probably be to compare schema versions,
but this seems to work well enough, and is better than _not_ handling it at all.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message