[
https://issues.apache.org/jira/browse/SOLR-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631063#comment-16631063
]
Mikhail Khludnev edited comment on SOLR-12798 at 9/28/18 6:31 AM:
------------------------------------------------------------------
This is somewhat -scary- interesting. see [^SOLR-12798-reproducer.patch]. If we
sent just one file it disables multipart and huge params might go to URL. After
that, test -*hangs*- fails with the log message
{quote}
390718 WARN (qtp1324113116-23) [ x:collection1] o.e.j.h.HttpParser URI is
too large >8192
HttpSolrClient$RemoteSolrException: Error from server at
http://127.0.0.1:55150/solr/collection1: Expected mime type
application/octet-stream but got text/html. <h1>Bad Message
414</h1><pre>reason: URI Too Long</pre>
{quote}
was (Author: mkhludnev):
This is somewhat scary. see [^SOLR-12798-reproducer.patch]. If we sent just one
file it disables multipart and huge params might go to URL. After that, test
*hangs* with the log message
{quote}
390718 WARN (qtp1324113116-23) [ x:collection1] o.e.j.h.HttpParser URI is
too large >8192
{quote}
> Structural changes in SolrJ since version 7.0.0 have effectively disabled
> multipart post
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-12798
> URL: https://issues.apache.org/jira/browse/SOLR-12798
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Affects Versions: 7.4
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Major
> Attachments: HOT Balloon Trip_Ultra HD.jpg,
> SOLR-12798-approach.patch, SOLR-12798-reproducer.patch, no params in url.png,
> solr-update-request.txt
>
>
> Project ManifoldCF uses SolrJ to post documents to Solr. When upgrading from
> SolrJ 7.0.x to SolrJ 7.4, we encountered significant structural changes to
> SolrJ's HttpSolrClient class that seemingly disable any use of multipart
> post. This is critical because ManifoldCF's documents often contain metadata
> in excess of 4K that therefore cannot be stuffed into a URL.
> The changes in question seem to have been performed by Paul Noble on
> 10/31/2017, with the introduction of the RequestWriter mechanism. Basically,
> if a request has a RequestWriter, it is used exclusively to write the
> request, and that overrides the stream mechanism completely. I haven't
> chased it back to a specific ticket.
> ManifoldCF's usage of SolrJ involves the creation of
> ContentStreamUpdateRequests for all posts meant for Solr Cell, and the
> creation of UpdateRequests for posts not meant for Solr Cell (as well as for
> delete and commit requests). For our release cycle that is taking place
> right now, we're shipping a modified version of HttpSolrClient that ignores
> the RequestWriter when dealing with ContentStreamUpdateRequests. We
> apparently cannot use multipart for all requests because on the Solr side we
> get "pfountz Should not get here!" errors on the Solr side when we do, which
> generate HTTP error code 500 responses. That should not happen either, in my
> opinion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
