You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jack Krupansky (JIRA)" <ji...@apache.org> on 2012/06/04 00:49:22 UTC
[jira] [Commented] (SOLR-3505) Detect and report when the limit for
maximum number of documents in a single index is exceeded
[ https://issues.apache.org/jira/browse/SOLR-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288277#comment-13288277 ]
Jack Krupansky commented on SOLR-3505:
--------------------------------------
Similar to LUCENE-4105, it would greatly simplify testing to have a mechanism for arbitrarily bumping the next document number to a value like Integer.MAX_VALUE - k so that the limit can be hit by adding only a small number of documents.
Although it might be necessary to add a handler-level request query parameter to set the document number, it may be sufficient for to have unit tests that reach in directly to the IndexWriter that Solr is using to set the document number.
But since it might be nice to be able to manually test (okay, scripted test) this feature with a full-blown multi-machine cloud cluster, an explicit request parameter might be more desirable. Maybe something like &__docNumber__=2147483630.
> Detect and report when the limit for maximum number of documents in a single index is exceeded
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-3505
> URL: https://issues.apache.org/jira/browse/SOLR-3505
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 3.6
> Reporter: Jack Krupansky
> Priority: Minor
>
> SOLR-3504 documents the limit for maximum number of documents in a single index, but it is highly desirable to have Solr detect when this limit is reached and provide a sensible response for the user.
> I am not sure of the implementation details, but generally each of the "update" handlers would return an HTTP 400 status code. The reason phrase should be something like "Exceeded maximum number of documents in a single index - 2,147,483,647".
> It is not clear whether Solr itself should check the limit defensively, or simply let Lucene throw the proposed MaxDocumentException and then catch it and return the desired 400 response. It is also not clear if that processing can be centralized or if calls to some new utility method would need to be sprinkled in various places in Solr. Add also it may or may not be necessary for update processors to either ignore or watch for this exception.
> There may be implications for SolrCloud, so that a reasonably useful response gets back to both the original poster code as well as the Solr admin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org