Home | About | Sematext search-lucene.com search-hadoop.com
 Search Lucene and all its subprojects:

Switch to Threaded View
Solr >> mail # user >> Negative value in numFound

Copy link to this message
Re: Negative value in numFound
"... is this limitation documented anywhere..."

Kind of, but not very well, at least at the Lucene level.

The Lucene File Formats page says "Lucene uses a Java int to refer to
document numbers, and the index file format uses an Int32 on-disk to store
document numbers. This is a limitation of both the index file format and the
current implementation." It also says that "The first document added to an
index is numbered zero." Since Java Integer.MAX_INT is 2^31-1, that means
the maximum number of documents in a single Lucene (or Solr) index is 2^31.


And the Lucene IndexSearcher API uses "int" for document number and number
of documents in index.

There is a little discussion of the limit issue here:

I am not aware of any explicit mention of the single-index Lucene document
limit at the Solr level.

-- Jack Krupansky

-----Original Message-----
From: tosenthu
Sent: Monday, May 28, 2012 11:34 AM
Subject: Re: Negative value in numFound


It is a multicore but when i searched the shards query even then i get this

<result name="response" numFound="-390662429" start="0">

which is again a negative value.

Might be the total number of records may be > 2147483647 (2^31-1), But is
this limitation documented anywhere. What is the strategy to over come this
situation. Expectation of my application is to have 12 billion records. So
please suggest me a strategy for my situation.

Senthil Kumar M R

View this message in context:
Sent from the Solr - User mailing list archive at Nabble.com.