[ 
https://issues.apache.org/jira/browse/SOLR-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-3218:
---------------------------
    Attachment: SOLR-3218.patch

Updated patch with a lot more {{json.facet}} tests.

While working on this i discovered SOLR-11824 -- these tests will currently 
fail very badly w/o the patch from SOLR-11824 also applied.

There is also still one test logic flaw in {{testJsonRangeFacetAsSubFacet}} 
because of SOLR-11733 ... i thought i had been creative enough in the 
documents/queries used to ensure that we'd get a consistent "top term" for 
these facets -- but I released later that with random sharding it's still 
possible to "miss" the term the test expects due to it being in the "long tail" 
... need to fix that.

bq. ...more notably because of the following points of confusion I have about 
the code in the existing patch that I'm hoping Yonik can provide some guidance 
on...

FWIW: I still haven't wrapped my head around these 2 questions.  Hoping i 
trigger some of these {{throw new RuntimeException("nocommit:...}} as i keep 
writing tests

> Range faceting support for CurrencyField
> ----------------------------------------
>
>                 Key: SOLR-3218
>                 URL: https://issues.apache.org/jira/browse/SOLR-3218
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Jan Høydahl
>            Assignee: Hoss Man
>         Attachments: SOLR-3218-1.patch, SOLR-3218-2.patch, SOLR-3218.patch, 
> SOLR-3218.patch, SOLR-3218.patch, SOLR-3218.patch, SOLR-3218.patch, 
> SOLR-3218.patch, SOLR-3218.patch, SOLR-3218.patch
>
>
> Spinoff from SOLR-2202. Need to add range faceting capabilities for 
> CurrencyField



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to