[
https://issues.apache.org/jira/browse/SOLR-17758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952634#comment-17952634
]
Jason Gerlowski commented on SOLR-17758:
----------------------------------------
(We discussed Rahul's comment above a bit in the PR. It indeed was a real
issue, and happened to be causing some test flakiness issues. It's fixed in
the commits referenced above. Thanks Rahul!)
> NumFieldLimiting URP "warnOnly" mode broken
> -------------------------------------------
>
> Key: SOLR-17758
> URL: https://issues.apache.org/jira/browse/SOLR-17758
> Project: Solr
> Issue Type: Bug
> Components: UpdateRequestProcessors
> Affects Versions: 9.8.1
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Labels: pull-request-available
> Fix For: main (10.0), 9.9
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> NumFieldLimitingUpdateProcessorFactory (introduced in SOLR-17192) aims to
> offer a "warnOnly" mode that logs a warning when the maximum number of fields
> is exceeded.
> But the "warnOnly" code path doesn't trigger any subsequent processors in the
> chain. So in effect, both modes will prevent new documents from being added
> once the limit has been exceeded.
> We should rework this logic so that the warnOnly=true codepath allows
> documents to be indexed as expected.
--
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
