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

Shai Erera resolved LUCENE-4882.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 4.3
                   5.0
         Assignee: Shai Erera
    Lucene Fields: New,Patch Available  (was: New)

Committed a fix to trunk and 4x. Thanks for reporting crocket!

If you cannot wait until 4.3 (and cannot work with 4x directly), you can use 
StandardFacetsAccumulator as an alternative, but note that it's slower than 
FacetsAccumulator. Or, create your own FacetsAccumulator and copy accumulate + 
fix.
                
> FacetsAccumulator.java:185 throws NullPointerException if it's given an empty 
> CategoryPath.
> -------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-4882
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4882
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/facet
>    Affects Versions: 4.2
>            Reporter: crocket
>            Assignee: Shai Erera
>            Priority: Critical
>             Fix For: 5.0, 4.3
>
>         Attachments: LUCENE-4882.patch
>
>
> When I wanted to count root categories, I used to pass "new CategoryPath(new 
> String[0])" to a CountFacetRequest.
> Since upgrading lucene from 4.1 to 4.2, that threw 
> ArrayIndexOfOutBoundsException, so I passed CategoryPath.EMPTY to a 
> CountFacetRequest instead, and this time I got NullPointerException.
> It all originates from FacetsAccumulator.java:185
> Does someone conspire to prevent others from counting root categories?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to