OK?
I get an error when I get the FC Insanity issue in SOLR-2242...
ant -Dtestcase=NumFacetTermsFacetsTest test
If it is normal, how do I turn off the FAILURE in the test case?
[junit] Testsuite: org.apache.solr.request.NumFacetTermsFacetsTest
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 4.072 sec
[junit]
[junit] ------------- Standard Error -----------------
[junit] NOTE: reproduce with: ant test
-Dtestcase=NumFacetTermsFacetsTest
-Dtestmethod=testNumFacetTermsFacetCounts
-Dtests.seed=3921835369594659663:-3219730304883530389
[junit] *** BEGIN
org.apache.solr.request.NumFacetTermsFacetsTest.testNumFacetTermsFacetCount
s: Insane FieldCache usage(s) ***
[junit] SUBREADER: Found caches for descendants of
DirectoryReader(segments_3 _0(4.0):C6)+hgid_i1
[junit] 'DirectoryReader(segments_3 _0(4.0):C6)'=>'hgid_i1',class
org.apache.lucene.search.FieldCache$DocTermsIndex,org.apache.lucene.search.
cache.DocTermsIndexCreator@603bb3eb=>org.apache.lucene.search.cache.DocTerm
sIndexCreator$DocTermsIndexImpl#1026179434 (size =~ 372 bytes)
[junit]
'org.apache.lucene.index.SegmentCoreReaders@7e8905bd'=>'hgid_i1',int,org.a
pache.lucene.search.cache.IntValuesCreator@30781822=>org.apache.lucene.sear
ch.cache.CachedArray$IntValues#291172425 (size =~ 92 bytes)
[junit]
[junit] *** END
org.apache.solr.request.NumFacetTermsFacetsTest.testNumFacetTermsFacetCount
s: Insane FieldCache usage(s) ***
On 7/1/11 6:54 AM, "Yonik Seeley" <[email protected]> wrote:
>On Thu, Jun 30, 2011 at 11:58 PM, Bill Bell <[email protected]> wrote:
>> I meant FC insanity. It does not appear to be an NPE.
>
>That's natural, and not a bug. Grouping always uses per-segment field
>cache entries, where faceting sometimes uses top level field caches.
>
>-Yonik
>http://www.lucidimagination.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
