Return-Path: X-Original-To: apmail-cassandra-dev-archive@www.apache.org Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EAF9B17E99 for ; Thu, 7 May 2015 17:22:44 +0000 (UTC) Received: (qmail 11183 invoked by uid 500); 7 May 2015 17:22:44 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 11141 invoked by uid 500); 7 May 2015 17:22:43 -0000 Mailing-List: contact dev-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 dev@cassandra.apache.org Received: (qmail 11120 invoked by uid 99); 7 May 2015 17:22:43 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 May 2015 17:22:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E591D182598 for ; Thu, 7 May 2015 17:22:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.881 X-Spam-Level: ** X-Spam-Status: No, score=2.881 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=datastax.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id YGWFm9nf6BtB for ; Thu, 7 May 2015 17:22:31 +0000 (UTC) Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id F144A23102 for ; Thu, 7 May 2015 17:22:30 +0000 (UTC) Received: by igbsb11 with SMTP id sb11so29741166igb.0 for ; Thu, 07 May 2015 10:21:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datastax.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=+0nhcHSZJM+FO7LiYERUZ71vmoCYtVCoO9dH0xuR0/E=; b=sael03qB5RzvCW1XpaiYYzxGovA/OymIkAc3arX5JQFu15nRIqPV+oSveV5h1h/G0M qMWuWXkFtfCPCk1aAwi238ldUESzy9znA0+NGVObNehYcQLo/cbahWIC83eq41eRwwkx 5X9Z3f6tw4ooucxErivlH+jYQgkT6usERr8OU= 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:from:date :message-id:subject:to:content-type; bh=+0nhcHSZJM+FO7LiYERUZ71vmoCYtVCoO9dH0xuR0/E=; b=Zv2C09oa9ACZfQT+0riwdZ72s0QUt3hZL4GS0fK/jGtX+wslMHQaj2CsuvmXomX3jz h2dlNDKc7TxsQFdTg2nqvPJwBK/RnpjtM7ANn/Z31r+3oOdtW2a7Q070F4ZoRtSsZ+Sv ckkGA0wrubsUpY2u6UY/Wp5V6vQuv20RMHA9IqUi6pUW581+ptkeWLyCgx2NjWKYS/Iq JmfSgVxBvvaDWXs14FxzMMi9n3jr8svUVFdw/KVeoZGfJP8SDZVwWDEOwMA2RJ4OONZs OxZsiPBjDbdMOr2VLLrr7nPfSVVmuc/qmkEC10I32suh2LJq3mXlPfZm8708cOpanUBU wpNg== X-Gm-Message-State: ALoCoQm1RY2G2FFwfWSioCFtOjSyZcW+0uDmF5UKOvLe9sOpkRLs4t1vXmuWgcnnpwy7Z/kWue3M X-Received: by 10.42.126.10 with SMTP id c10mr5007500ics.66.1431019305326; Thu, 07 May 2015 10:21:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.123.142 with HTTP; Thu, 7 May 2015 10:21:24 -0700 (PDT) In-Reply-To: References: From: Tyler Hobbs Date: Thu, 7 May 2015 12:21:24 -0500 Message-ID: Subject: Re: cqlsh client side filtering To: dev@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3011d9bb5c773605158125d8 --20cf3011d9bb5c773605158125d8 Content-Type: text/plain; charset=UTF-8 On Thu, May 7, 2015 at 10:42 AM, Jens Rantil wrote: > > Are there any plans (or JIRA issue) for adding client-side filtering to > cqlsh? It would hugely improve our experiences with it when debugging etc. > I wouldn't be against adding some kind of auto LIMIT or warning when using > it as I understand users could use it as an anti-pattern, too. There are general plans to increase the types of filtering that Cassandra can do server-side, but CASSANDRA-8099 is necessary for a lot of that work. We prefer not to support things in cqlsh that can't be done through normal cql queries (outside of basic admin-type operations). What sort of API are you envisioning? -- Tyler Hobbs DataStax --20cf3011d9bb5c773605158125d8--