You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/04/19 03:38:00 UTC
[jira] [Commented] (SOLR-12142) EmbeddedSolrServer should use
req.getContentWriter
[ https://issues.apache.org/jira/browse/SOLR-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443535#comment-16443535 ]
ASF subversion and git services commented on SOLR-12142:
--------------------------------------------------------
Commit 1c8ab330d66557a289dd5398576726a43964c9e8 in lucene-solr's branch refs/heads/master from noble
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1c8ab33 ]
SOLR-12142: EmbeddedSolrServer should use req.getContentWriter
> EmbeddedSolrServer should use req.getContentWriter
> ---------------------------------------------------
>
> Key: SOLR-12142
> URL: https://issues.apache.org/jira/browse/SOLR-12142
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: Noble Paul
> Priority: Major
> Attachments: SOLR-12142.patch
>
>
> In SOLR-11380, SolrRequest.getContentWriter was introduced as a replacement for getContentStreams. However, EmbeddedSolrServer still calls getContentStreams, and so clients who need to send POST data to it cannot yet switch from the Deprecated API to the new API. The SolrTextTagger is an example of a project where one would want to do this.
> It seems EmbeddedSolrServer ought to check for getContentWriter and if present then convert it into a ContentStream somehow. For the time being, ESS needs to call both since both APIs exist.
> CC [~noble.paul]
--
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