Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E733218A01 for ; Tue, 14 Jul 2015 22:18:04 +0000 (UTC) Received: (qmail 64545 invoked by uid 500); 14 Jul 2015 22:18:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 64500 invoked by uid 500); 14 Jul 2015 22:18:04 -0000 Mailing-List: contact commits-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 commits@cassandra.apache.org Received: (qmail 64485 invoked by uid 99); 14 Jul 2015 22:18:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2015 22:18:04 +0000 Date: Tue, 14 Jul 2015 22:18:04 +0000 (UTC) From: "Tyler Hobbs (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9802) Better page size for aggregates in cqlsh MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627143#comment-14627143 ] Tyler Hobbs commented on CASSANDRA-9802: ---------------------------------------- What about picking a page size server-side based on the average row size for the table? It wouldn't be perfect, but doing it based on our metrics would probably be better than (99% of) users could do manually. As a bonus, it fixes the cqlsh problem. > Better page size for aggregates in cqlsh > ---------------------------------------- > > Key: CASSANDRA-9802 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9802 > Project: Cassandra > Issue Type: Improvement > Reporter: Sylvain Lebresne > Assignee: Benjamin Lerer > Priority: Minor > Fix For: 3.x > > > As discussed in CASSANDRA-9724, cqlsh uses a small page size (100) which makes sense for "normal" queries since you don't want to flood the terminal, but is quite sub-optimal for aggregates where the page size is used as the internal page size for the aggregate (there is thus no terminal flooding concerns and a page size of 100 is too low). > We should thus make cqlsh use a bigger page size (stick with the python driver default for instance) when dealing with aggregate queries. According to Tyler: > bq. it's not trivial, but it is possible. It should take a day or less of work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)