Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-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 79C8517745 for ; Tue, 28 Oct 2014 14:30:34 +0000 (UTC) Received: (qmail 61930 invoked by uid 500); 28 Oct 2014 14:30:34 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 61873 invoked by uid 500); 28 Oct 2014 14:30:34 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 61857 invoked by uid 99); 28 Oct 2014 14:30:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2014 14:30:34 +0000 Date: Tue, 28 Oct 2014 14:30:34 +0000 (UTC) From: "Ben Keen (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work stopped] (COUCHDB-2412) group_level exact should explicitly pass value 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/COUCHDB-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on COUCHDB-2412 stopped by Ben Keen. ----------------------------------------- > group_level exact should explicitly pass value > ---------------------------------------------- > > Key: COUCHDB-2412 > URL: https://issues.apache.org/jira/browse/COUCHDB-2412 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton > Reporter: Ben Keen > Assignee: Ben Keen > > Right now when you do a search on a View with group level = exact, it doesn't pass any group_level value. > This can be solved in one of two ways: > - Pass a really high level for the group_level value (999) > - pass group=true instead. > Option #2 is way nicer, so let's do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)