Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9EFF910E85 for ; Fri, 28 Aug 2015 09:25:48 +0000 (UTC) Received: (qmail 10596 invoked by uid 500); 28 Aug 2015 09:25:48 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 10556 invoked by uid 500); 28 Aug 2015 09:25:48 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 10544 invoked by uid 99); 28 Aug 2015 09:25:48 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2015 09:25:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 18C281AAFD9 for ; Fri, 28 Aug 2015 09:25:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.774 X-Spam-Level: * X-Spam-Status: No, score=1.774 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.006] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JTsOXHU6LYT5 for ; Fri, 28 Aug 2015 09:25:47 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 0D18950703 for ; Fri, 28 Aug 2015 09:25:46 +0000 (UTC) Received: (qmail 10332 invoked by uid 99); 28 Aug 2015 09:25:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2015 09:25:46 +0000 Date: Fri, 28 Aug 2015 09:25:46 +0000 (UTC) From: "Ajay Yadava (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FALCON-877) Pagination API should have a cap on number of results returned 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/FALCON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Yadava updated FALCON-877: ------------------------------- Fix Version/s: (was: 0.7) 0.6.1 > Pagination API should have a cap on number of results returned > -------------------------------------------------------------- > > Key: FALCON-877 > URL: https://issues.apache.org/jira/browse/FALCON-877 > Project: Falcon > Issue Type: Improvement > Affects Versions: 0.6 > Reporter: Ajay Yadava > Assignee: Ajay Yadava > Fix For: 0.6.1 > > Attachments: FALCON-877-v1.patch, FALCON-877-v2.patch, FALCON-877.patch > > > Currently one can specify any arbitrary large number for number of results and falcon will return "all" or the specified number of results (whichever is smaller). This defeats the purpose of pagination as users can still ask for all the results in one go. There should be an upper bound on number of results to be returned by client/service calls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)