Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 82017 invoked from network); 6 Oct 2009 21:38:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Oct 2009 21:38:38 -0000 Received: (qmail 7920 invoked by uid 500); 6 Oct 2009 21:38:38 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 7901 invoked by uid 500); 6 Oct 2009 21:38:38 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 7892 invoked by uid 99); 6 Oct 2009 21:38:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 21:38:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jgirtakovskis@gmail.com designates 209.85.220.209 as permitted sender) Received: from [209.85.220.209] (HELO mail-fx0-f209.google.com) (209.85.220.209) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 21:38:27 +0000 Received: by fxm5 with SMTP id 5so3878041fxm.27 for ; Tue, 06 Oct 2009 14:37:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=NccXMYAM/8aRKyqfmhCI/InEGktJiUG7C/qTKDfsjb4=; b=c5jsZWuBZ/IEnqkTDS7h2L8Ir1U49vqL52wB7CgejV3m2tvcI6511dhz0iw9GJ1PE6 AaZ1fz0GYXLTMXKyrq4EUEeCMihBtZq5ipOPzno3Sihfumt/AXdnH8xT3U2AoZsrXnGh TMC0va9rp7KSy64mPdS2zCzNnB9/OzdlFsDg4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=URcTcynKLgau3PAlr6zwU6AccgBFCSIgmiS+x9yZbz7MEYqq4hubK42uJhcKDaB8Mn CMmilEcdi5/KUQa0HccLsETorpHQHjCiGHcZbSuW9GLZXETleDTojxLUYu4KQFdV0gJN t42RlWqv1nqQ71s4KdD2CeRGIDAdcbPzlnTv4= Received: by 10.103.85.28 with SMTP id n28mr599172mul.66.1254865027733; Tue, 06 Oct 2009 14:37:07 -0700 (PDT) Received: from ?192.168.110.221? ([69.15.141.26]) by mx.google.com with ESMTPS id j9sm311029mue.56.2009.10.06.14.37.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 06 Oct 2009 14:37:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v1076) Subject: cassandra upgrade strategy From: Jurijs Girtakovskis In-Reply-To: Date: Tue, 6 Oct 2009 15:37:04 -0600 Content-Transfer-Encoding: 7bit Message-Id: <9069C645-451C-4BEE-B13F-BA5FCAEBCCEE@gmail.com> References: To: cassandra-user@incubator.apache.org X-Mailer: Apple Mail (2.1076) X-Virus-Checked: Checked by ClamAV on apache.org Hi, What would be the direction to take as far as preparing for future cassandra updates? My understanding is that there were changes between 0.3 and 0.4 that required extra work to port (some?) data from older format, please correct me if I'm wrong. If that's the case and/or if that is a possibility in future, then what would be the right approach to take for those considering Cassandra 0.4 for production? I currently see three possibilities: 1. That will never happen - formats will always stay compatible and newer version will be able to take older data and use it. Nothing to do for me. 2. That may happen, but if it does, there will be a conversion utility (built-in or standalone) taking care of upgrade. Nothing to do for me, other than running upgrade tool. 3. That may happen, and if it does data conversion must be performed using custom tools. Custom upgrade tool needed. Thank you in advance for your constructive feedback and/or pointers to resources that lead to answers! -JG