You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2018/09/24 09:09:00 UTC
[jira] [Comment Edited] (SOLR-12798) Structural changes in SolrJ
since version 7.0.0 have effectively disabled multipart post
[ https://issues.apache.org/jira/browse/SOLR-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625558#comment-16625558 ]
Karl Wright edited comment on SOLR-12798 at 9/24/18 9:08 AM:
-------------------------------------------------------------
We're researching the actual issue that is blocking release. It seems that deleting documents using a Solr Cloud installation may not be working; for each document, we're seeing a 400 error with the following message:
{code}
Error from server at http://localhost:8983/solr/FileShare_shard1_replica_n1: missing content stream: Error from server at http://localhost:8983/solr/FileShare_shard1_replica_n1: missing content stream
{code}
Furthermore, after checking the Solr index, none of the documents have been removed.
This is obviously severe and we're trying now to confirm that this happens without our modifications to HttpSolrClient.
was (Author: kwright@metacarta.com):
We're researching the actual issue that is blocking release. It seems that deleting documents using a Solr Cloud installation may not be working; for each document, we're seeing a 400 error with the following message:
Error from server at http://localhost:8983/solr/FileShare_shard1_replica_n1: missing content stream: Error from server at http://localhost:8983/solr/FileShare_shard1_replica_n1: missing content stream
Furthermore, after checking the Solr index, none of the documents have been removed.
This is obviously severe and we're trying now to confirm that this happens without our modifications to HttpSolrClient.
> 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: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Affects Versions: 7.4
> Reporter: 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org