Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-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 CF62717AE4 for ; Mon, 27 Oct 2014 23:36:34 +0000 (UTC) Received: (qmail 62976 invoked by uid 500); 27 Oct 2014 23:36:33 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 62907 invoked by uid 500); 27 Oct 2014 23:36:33 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 62895 invoked by uid 99); 27 Oct 2014 23:36:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Oct 2014 23:36:33 +0000 Date: Mon, 27 Oct 2014 23:36:33 +0000 (UTC) From: "Hoss Man (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SOLR-6663) decide rules & syntax for computing stats/ranges/queries only at certain levels of a pivot MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Hoss Man created SOLR-6663: ------------------------------ Summary: decide rules & syntax for computing stats/ranges/queries only at certain levels of a pivot Key: SOLR-6663 URL: https://issues.apache.org/jira/browse/SOLR-6663 Project: Solr Issue Type: Sub-task Reporter: Hoss Man [~smolloy] asked a great question in SOLR-6351... bq. One more question around this, which applies for SOLR-6353 and SOLR-4212 as well. Should we have a syntax to apply stats/queries/ranges only at specific levels in the pivot hierarchy? It would reduce amount of computation and size of response for cases where you only need it at a specific level (usually last level I guess). I'm splitting this off into it's own Sub-task for further discussion. ---- For now, the "stats" localparam must be a single tag, and the "work around" is to add a common tag to all stats you want to use. ie, this will cause an error... {noformat} stats.field={!tag=tagA}price stats.field={!tag=tagB}popularity stats.field={!tag=tagB}clicks facet.pivot={!stats=tagA,tagB}xxx,yyy,zz {noformat} but this will work... {noformat} stats.field={!tag=tagA,tagPivot}price stats.field={!tag=tagB,tagPivot}popularity stats.field={!tag=tagB,tagPivot}clicks facet.pivot={!stats=tagPivot}xxx,yyy,zz {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org