[
https://issues.apache.org/jira/browse/SOLR-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720492#comment-13720492
]
Shawn Heisey commented on SOLR-5077:
------------------------------------
It seems to me that formdataUploadLimitInKB is typically more useful than its
multipart cohort, so IMHO we need that in all the examples. We probably do NOT
need either setting in the test-files configs. I'm not sure that the multipart
version needs to be there, but I'm OK with it remaining. I'd just like to get
a feel for what everyone thinks is the best way to go.
I think we probably want to change all the 2048000 entries to 2048. I doubt
that any of the tests actually need a multipart buffer that big, but if any do,
please let me know.
Off to bed, I'll make a patch tomorrow.
> Inconsistencies in solrconfig upload limits - examples and test-files
> ---------------------------------------------------------------------
>
> Key: SOLR-5077
> URL: https://issues.apache.org/jira/browse/SOLR-5077
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.4
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 5.0, 4.5
>
>
> In the various solrconfig.xml files, there is no consistency in how the
> request parser upload limits are configured. In some of them, only
> multipartUploadLimitInKB is configured. In others, formdataUploadLimitInKB
> is also defined. Most of them have a multipart value of 2048, but a few
> (including the main example) have 2048000, which represents nearly 2GB
> instead of 2MB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
