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

crocket closed LUCENE-4912.
---------------------------

    Resolution: Invalid

This is not an issue, but a mistake by a user
                
> ArrayIndexOutOfBoundsException from FastCountingFacetsAggregator.java:86
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-4912
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4912
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/facet
>    Affects Versions: 4.2
>            Reporter: crocket
>            Priority: Blocker
>
> I have a play framework project that uses lucene, which is hosted on 
> git://snowberry.me/ZeroIrcLog.git
> After stopping a running instance of it with Ctrl+D(play framework supports 
> this shortcut), whenever I try to run it by "play run", I see
> Exception in thread "Thread-5" java.lang.ArrayIndexOutOfBoundsException: 2
>       at 
> org.apache.lucene.facet.search.FastCountingFacetsAggregator.aggregate(FastCountingFacetsAggregator.java:86)
>       at 
> lucene42fix.FacetsAccumulatorWithDimensionFix.accumulate(FacetsAccumulatorWithDimensionFix.java:37)
>       at 
> org.apache.lucene.facet.search.FacetsCollector.getFacetResults(FacetsCollector.java:207)
>       at 
> org.zeroirclog.LuceneLoggerWorker.processControlMessage(LuceneLoggerWorker.java:292)
>       at org.zeroirclog.LuceneLoggerWorker.run(LuceneLoggerWorker.java:191)
>       at org.zeromq.ZThread$ShimThread.run(ZThread.java:48)
> It seems TaxonomyWriter creates org.apache.lucene.store.MMapDirectory\@ 
> instead of the actual taxonomy index directory.

--
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