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 EF50E1A48 for ; Wed, 20 Apr 2011 22:41:46 +0000 (UTC) Received: (qmail 314 invoked by uid 500); 20 Apr 2011 22:41:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 290 invoked by uid 500); 20 Apr 2011 22:41:45 -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 282 invoked by uid 99); 20 Apr 2011 22:41:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2011 22:41:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brailateo@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2011 22:41:38 +0000 Received: by bwz13 with SMTP id 13so1142975bwz.31 for ; Wed, 20 Apr 2011 15:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=+8qGffMgH7t4N0UoSgfIB+4N5ftM+ETL5X74idMFUFM=; b=SlmgY4KbUMWTzQDB0kkVhLNwgLmsjQAvmYqE6xDVgjH9sPzpWnacl1AXhLmXR7xFW9 Jau5H3Di05DUItBR8g+58ZifoRa2TeIfVMRQhunO+UvGbJLXPMshkyBddCJwVg/+Or6D YGJvOJhYv+ndH/PUZ2mqpFPYCIPLc6/p0SaL4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=EqiUrWBh430ILzTiKPzidGHhsomUUD/JoAJ0Q3OuM3hPY3eri0RAdHoqbyvyNcY5zn t8uCMgL1xjHz6DnqShpPNzRdvAf4h10BOnOQXZOHg98Qz8oSqUGGREBMCLufBpayL7WM 2rrXXVoxVN8/HNpBc4IE16osdErcO8iCdYVfQ= Received: by 10.204.85.8 with SMTP id m8mr4835025bkl.139.1303339277189; Wed, 20 Apr 2011 15:41:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.51.20 with HTTP; Wed, 20 Apr 2011 15:40:57 -0700 (PDT) From: Constantin Teodorescu Date: Thu, 21 Apr 2011 01:40:57 +0300 Message-ID: Subject: CQL in future 8.0 cassandra will work as I'm expecting ? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e6d97286a3815104a16152fe --0016e6d97286a3815104a16152fe Content-Type: text/plain; charset=ISO-8859-1 My use case is as follows: we are using in 70% of the jobs information retrieval using keys, column names and ranges and up to now, what we have tested suits our need. However, the rest of 30% of the jobs involve full sequential scan of all records in the database. I found some web pages describing the next good thing for cassandra 0.8 release, CQL, and I'm wondering: the CQL execution will involve separate processes running simultaneously on all nodes in the cluster that will do the "filtering and pre-sorting phase" on the local stored data (using indexes when available) and then execute the "merge phase" on a single node (that one that have received the request) ? Best regards, Teo --0016e6d97286a3815104a16152fe Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable My use case is as follows: we are using in 70% of the jobs information retr= ieval using keys, column names and ranges and up to now, what we have teste= d suits our need.
However, the rest of 30% of the jobs involve full seq= uential scan of all records in the database.

I found some web pages describing the next good thing f= or cassandra 0.8 release, CQL, and I'm wondering: the CQL execution wil= l involve separate processes running simultaneously on all nodes in the clu= ster that will do the "filtering and pre-sorting phase" on the lo= cal stored data (using indexes when available) and then execute the "m= erge phase" on a single node (that one that have received the request)= ?

Best regards,
Teo

--0016e6d97286a3815104a16152fe--