[
https://issues.apache.org/jira/browse/SOLR-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608409#comment-17608409
]
Jason Gerlowski commented on SOLR-16428:
----------------------------------------
I've opened up a new PR for this
[here|https://github.com/apache/solr/pull/1040]. It still needs tests and
documentation in the ref-guide, but otherwise was pretty straightforward!
> IgnoreLargeDocumentsProcessorFactory should have a "permissive" mode
> --------------------------------------------------------------------
>
> Key: SOLR-16428
> URL: https://issues.apache.org/jira/browse/SOLR-16428
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
> Affects Versions: 9.0, main (10.0)
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IgnoreLargeDocumentProcessorFactory only has a single way to handle documents
> that exceed its configurable size limit. The first violation throws a
> SolrException: in effect, short-circuiting any remaining documents in the
> "batch" and returning a 400 to the user.
> This is great for end users whose clients are built to handle the resulting
> 400 response, and who can modify and resubmit the batch. But it's not ideal
> for every use-case, especially where "best-effort" indexing is good enough.
> This ticket proposes adding a new "permissive" mode of handling too-large
> documents to ILDPF. Under this new mode "too-large" documents will be logged
> (and not indexed), but won't cause the entire batch to be aborted/error-out.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
