[
https://issues.apache.org/jira/browse/SOLR-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628912#comment-16628912
]
Noble Paul commented on SOLR-12798:
-----------------------------------
bq.How many examples do you need to convince yourselves that we're not making
this up?
Looks like you don't understand the objectives here. We design SolrJ client and
server with certain usecases in mind. While doing that we assume that we meet
the needs of most/all users. The fact that you had to implement a custom client
suggests that either we have failed in that or you have failed in understanding
how SolrJ works . I'm sure you wouldn't open a ticket to waste our time. We
have also come across so many cases were users are "holding it wrong" . That is
why a specific example is useful. If we realize that there is a genuine use
case that cannot be satisfied by the state-of-the-art SolrJ client, we will
work towards improving our code so that you don't have to do the dirty work.
The objective of Solr is not to support multipart form posts . It is designed
to send in docs/commands and get out query results. The multipart mechanism is
just a means to an end. Imagine, Solr working on a non HTTP standard. In that
case we still need to support all these use cases. So, please be patient if we
are trying to get details
> 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
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
