[
https://issues.apache.org/jira/browse/SOLR-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458656#comment-16458656
]
David Smiley commented on SOLR-12278:
-------------------------------------
{quote}If you want to reject large requests, configure Jetty to reject large
requests.
{quote}
If it's streaming (Content-Length header is \-1) then Jetty won't know. And
even for gigabytes of streaming data through it's not necessarily a problem at
all -- it could be lots of reasonably sized documents.
A few hours ago I wondered if we could solve this in a lower level more
efficient way. It's a shame to measure this stuff after it's been deserialized
when Solr is in fact reading the bytes and knows how many bytes were read when
the SolrInputDocument finishes. To this end, imagine if FastInputStream had
methods to track the overall bytes written and then JavaBinCodec could use that
information. Granted an on-the-wire bytes != Java heap bytes... and of course
what if someone sends the data in CSV or XML or JSON... but nonetheless it
could be a bonus feature of JavaBin that would be exceptionally cheap to
calculate and very little LOC.
> Ignore very large document on indexing
> --------------------------------------
>
> Key: SOLR-12278
> URL: https://issues.apache.org/jira/browse/SOLR-12278
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12278.patch, SOLR-12278.patch
>
>
> Solr should be able to ignore very large document, so it won't affect the
> index as well as the tlog.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
