Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9ABEFF4BF for ; Fri, 29 Mar 2013 15:51:19 +0000 (UTC) Received: (qmail 17296 invoked by uid 500); 29 Mar 2013 15:51:19 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 16901 invoked by uid 500); 29 Mar 2013 15:51:17 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 16499 invoked by uid 99); 29 Mar 2013 15:51:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 15:51:15 +0000 Date: Fri, 29 Mar 2013 15:51:15 +0000 (UTC) From: "Carl Yeksigian (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5378) Fat Client: No longer works in 1.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Yeksigian updated CASSANDRA-5378: -------------------------------------- Attachment: 5378-v2.txt This fixes the test. > 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