yes, re-indexed after changing the schema
select?q=*:*&wt=json&debugQuery=true&indent=true&rows=0&fq=date%3A%5B2013-08-17T00%3A00%3A00Z+TO+2015-08-17T00%3A00%3A00Z%5D&json.facet={facet1:{range:{end:'NOW/DAY',facet:{namefacet:{terms:{facet:{facet2:{terms:{facet:{sum:"sum(amount)"},field:city,mincount:1}}},field:name,mincount:1}}},start:'NOW-2YEARS/DAY',field:date,gap:'%2B1DAYS'}}}
On Mon, Aug 24, 2015 at 6:50 PM, Yonik Seeley <ysee...@gmail.com> wrote:
> On Mon, Aug 24, 2015 at 6:33 PM, naga sharathrayapati
> <sharathrayap...@gmail.com> wrote:
> > In order to improve the query time of nested faceting query (json facet
> > api), have used 'docValues' in the schema,optimized index and increased
> > cache sizes(no evictions)
> >
> > I still cannot be bring the query time to less than 1 sec.
> >
> > is there anything that i can do that can improve the performance?
>
> What does the json facet request look like?
>
> If you haven't already, you could try 5.3 as well... it could help if
> you're calculating any facet functions that you aren't sorting by.
>
> http://yonik.com/download/
>
> -Yonik
>
