Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 152F911A25 for ; Sat, 26 Jul 2014 08:10:45 +0000 (UTC) Received: (qmail 29474 invoked by uid 500); 26 Jul 2014 08:10:42 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 29434 invoked by uid 500); 26 Jul 2014 08:10:42 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 29405 invoked by uid 99); 26 Jul 2014 08:10:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jul 2014 08:10:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jul 2014 08:10:36 +0000 Received: by mail-wi0-f181.google.com with SMTP id bs8so2023694wib.14 for ; Sat, 26 Jul 2014 01:10:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OTvaJVD28SEhcdE0t1JTN+TqdkKqKe6ml8nIKxinLoA=; b=Bna6Hphtyk8cnoYZik567Xu91i16SkBeOKp5rxVLPtND71KuMhDSaDiGCuvs4aRgW+ oX0ZDtWUFPJZmcu2HVb2wpZJf6EkFCVzbPLxd28ena38jLIEmpJPNxSUAc9I+DW25ANk Ytu8ddFrguWmVDKPhvrY6qFl/gICzALjpRxoQd9EeVwcHiOmAOKSOglWc/e4fHlnmXA3 8FfDuN5Qhn/HyHmOuYHNF4iB45kU6RGTFEYWnw9EV5Lpo4KC7z6zwojyU0gHOtEuCmVM mLtSm8rDr4FQcytw3g5Zah9SbFoy+Wfmm7swGmKIogRJ2gPKw6o6Uz0IIOOtOHqg4z7s GHlg== X-Gm-Message-State: ALoCoQkstazvdPFdaNbwsqHMkMpIMcv7J8Z89at6h1hnAaZrBXhW+yBkPiiHa/Zi3u2KKjUcYXHe MIME-Version: 1.0 X-Received: by 10.194.142.148 with SMTP id rw20mr28255300wjb.69.1406362214625; Sat, 26 Jul 2014 01:10:14 -0700 (PDT) Received: by 10.194.55.135 with HTTP; Sat, 26 Jul 2014 01:10:14 -0700 (PDT) X-Originating-IP: [95.44.90.230] In-Reply-To: <883FC877-3C6E-4FA4-810A-C95EB8B51B7F@rahul.be> References: <883FC877-3C6E-4FA4-810A-C95EB8B51B7F@rahul.be> Date: Sat, 26 Jul 2014 09:10:14 +0100 Message-ID: Subject: Re: Cassandra version upgrade path From: Mark Reddy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e013a27c43a912704ff1438f7 X-Virus-Checked: Checked by ClamAV on apache.org --089e013a27c43a912704ff1438f7 Content-Type: text/plain; charset=UTF-8 Check https://github.com/apache/cassandra/blob/trunk/NEWS.txt to see the steps required, if any, when upgrading. As a general practice you should also reviw the changes at https://github.com/apache/cassandra/blob/trunk/CHANGES.txt If upgrading major versions it is often recommended to be on the latest version of your current major version first before attempting an upgrade and test in a non production environment beforehand. Mark On Sat, Jul 26, 2014 at 8:01 AM, Rahul Neelakantan wrote: > Is there a tool/guide/document that shows you upgrade paths for different > versions of Cassandra? > > For example if you are on version X and want to go to version Y, here are > the intermediate versions you need to upgrade to and here are some special > precautions/Steps you need to take for so and so version while upgrading > > Rahul Neelakantan > 678-451-4545 --089e013a27c43a912704ff1438f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Check https://github.com/apache/cassandra/blob/trunk/NEWS.txt= to see the steps required, if any,=C2=A0when upgrading.=C2=A0

=
As a general practice you should also reviw the changes at https://github.com/a= pache/cassandra/blob/trunk/CHANGES.txt If upgrading major versions it i= s often recommended to be on the latest version of your current major versi= on first before attempting an upgrade and test in a non production environm= ent beforehand.


Mark


On Sat, Jul 26, 2014 at 8:01 AM, Rahu= l Neelakantan <rahul@rahul.be> wrote:
Is there a tool/guide/document that shows yo= u upgrade paths for different versions of Cassandra?

For example if you are on version X and want to go to version Y, here are t= he intermediate versions you need to upgrade to and here are some special p= recautions/Steps you need to take for so and so version while upgrading

Rahul Neelakantan
678-451-4545
=

--089e013a27c43a912704ff1438f7--