ve been inserted. Instead, you get this error
> when Solr tries to read such an overstuffed index.
>
> -- Jack Krupansky
>
> -Original Message- From: [Tech Fun]山崎
> Sent: Tuesday, May 6, 2014 8:54 PM
> To: solr-user@lucene.apache.org
> Subject: Too many documents Exceptio
Sent: Wednesday, May 7, 2014 8:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Too many documents Exception
Tanks, Jack.
Is there a way to suppress setting this exception?
For example,
2147483647 ?
When this exception occurs, Index will not be read.
If solrcloud is used, some data not
ate: Wed, 7 May 2014 09:54:54 +0900
: From: "[Tech Fun]山崎"
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Too many documents Exception
:
: Hello everybody,
:
: Solr 4.3.1(and 4.7.1), Num Docs + Deleted Docs >
: 2147483647(In
Looks like you've hit an internal limitation of Lucene, see
http://lucene.apache.org/core/3_0_3/fileformats.html#Limitations:
When referring to term numbers, Lucene's current implementation uses a
Java int to hold the term index, which means the maximum number of unique terms
in any sin
You'll need to shard your index. This assumes that your index doesn't
have a huge percentage of deleted docs. This latter shouldn't be
happening since as you delete docs, the number of deleted docs should
drop as segments are merged.
I suspect you aren't searching on this index yet, because I'm pr
ad such an overstuffed index.
-- Jack Krupansky
-Original Message-
From: [Tech Fun]山崎
Sent: Tuesday, May 6, 2014 8:54 PM
To: solr-user@lucene.apache.org
Subject: Too many documents Exception
Hello everybody,
Solr 4.3.1(and 4.7.1), Num Docs + Deleted Docs >
2147483647(Integer.MAX_VALUE
Hello everybody,
Solr 4.3.1(and 4.7.1), Num Docs + Deleted Docs >
2147483647(Integer.MAX_VALUE) over
Caused by: java.lang.IllegalArgumentException: Too many documents,
composite IndexReaders cannot exceed 2147483647
It seems to be trouble similar to the unresolved e-mail.
http://mail-archives.apa
