Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 50303 invoked from network); 11 Jun 2009 23:54:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jun 2009 23:54:05 -0000 Received: (qmail 46748 invoked by uid 500); 11 Jun 2009 23:54:17 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 46674 invoked by uid 500); 11 Jun 2009 23:54:17 -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 46663 invoked by uid 99); 11 Jun 2009 23:54:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jun 2009 23:54:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists+1244763638173-3065146@n2.nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jun 2009 23:53:48 +0000 Received: from tervel.nabble.com ([192.168.236.150]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MEu5F-0001z1-Ll for cassandra-user@incubator.apache.org; Thu, 11 Jun 2009 16:53:25 -0700 Message-ID: <1244764405669-3065200.post@n2.nabble.com> Date: Thu, 11 Jun 2009 16:53:25 -0700 (PDT) From: testn To: cassandra-user@incubator.apache.org Subject: Database backstore MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: test1@doramail.com X-Virus-Checked: Checked by ClamAV on apache.org Is it possible to persist the data into the database and using cassandra as a cache writethrough? I wonder this because many organizations don't really quite believe in the reliability of disk storage (i.e. can be corrupted). If Cassandra can load data from Database on the fly while persisting it into the database when writing, it would be perfect.. -- View this message in context: http://n2.nabble.com/Database-backstore-tp3065200p3065200.html Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.