cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2
Date Mon, 13 May 2013 10:41:15 GMT

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

Carl Yeksigian commented on CASSANDRA-5378:
-------------------------------------------

The point of the second patch was to prevent us from using the file system. This means that
the migration manager probably needs to be able to operate exclusively in memory.

I'll take a look at this issue later today.
                
> Fat Client: No longer works in 1.2
> ----------------------------------
>
>                 Key: CASSANDRA-5378
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>              Labels: client
>             Fix For: 1.2.4
>
>         Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt
>
>
> The current client only example doesn't compile. After doing some updates, the fat client
still won't work, mainly because the schema is not being pushed to the fat client.
> I've made changes to the client to support CQL3 commands, to the ServiceManager to wait
until a migration has completed before starting the client, and to the MigrationManager to
not try to pull schemas from a fat client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message