Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 71239 invoked from network); 16 Sep 2008 06:26:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Sep 2008 06:26:07 -0000 Received: (qmail 76920 invoked by uid 500); 16 Sep 2008 06:26:02 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 76892 invoked by uid 500); 16 Sep 2008 06:26:02 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 76881 invoked by uid 99); 16 Sep 2008 06:26:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Sep 2008 23:26:02 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2008 06:25:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2302B234C1D8 for ; Mon, 15 Sep 2008 23:25:45 -0700 (PDT) Message-ID: <505030759.1221546345142.JavaMail.jira@brutus> Date: Mon, 15 Sep 2008 23:25:45 -0700 (PDT) From: "Joydeep Sen Sarma (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4086) Add limit to Hive QL In-Reply-To: <1193984713.1220636566114.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631263#action_12631263 ] Joydeep Sen Sarma commented on HADOOP-4086: ------------------------------------------- one thing i found fairly ridiculous is that the current select * from actually runs a map-reduce job. we have to fix this :-). if the LimitMapOp can be run in a separate client side task that dumps to console instead of to a file (in case we are not emitting to a table) - that would kill two birds with one stone. the limit in the inner clause is interesting. how we wish there was a no-sort option for map-reduce! the sorting is high overhead - so a separate concatenator task (which may still be run on the cluster where the concatenation runs inside a single mapper no-reducer map-reduce job) may be better. (that is assuming we are doing a redundant sort - which may not be true in all cases). > Add limit to Hive QL > -------------------- > > Key: HADOOP-4086 > URL: https://issues.apache.org/jira/browse/HADOOP-4086 > Project: Hadoop Core > Issue Type: New Feature > Components: contrib/hive > Reporter: Ashish Thusoo > Assignee: Ashish Thusoo > > Add a limit feature to the Hive Query language. > so you can do the following things: > SELECT * FROM T LIMIT 10; > and this would just return the 10 rows. > No gaurantees are made on which 10 rows are returned by the query. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.