[
https://issues.apache.org/jira/browse/SOLR-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999419#comment-15999419
]
Shawn Heisey commented on SOLR-8339:
------------------------------------
How does one actually convert SolrDocument to SolrInputDocument without the
methods that no longer exist? This was discussed today in the #solr IRC
channel, and the following SO post was mentioned: I tried a few ideas, but was
unable to
http://stackoverflow.com/questions/38266684/substitute-of-org-apache-solr-client-solrj-util-clientutils-tosolrinputdocument
I've come up with an alternate plan to restoring the ClientUtils method -- a
constructor on SolrDocumentBase that accepts another SolrDocumentBase as an
argument, and does a shallow copy.
> SolrDocument and SolrInputDocument should have a common interface
> -----------------------------------------------------------------
>
> Key: SOLR-8339
> URL: https://issues.apache.org/jira/browse/SOLR-8339
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: Shalin Shekhar Mangar
> Fix For: 5.5, 6.0
>
> Attachments: SOLR-8339.patch, SOLR-8339.patch, SOLR-8339.patch,
> SOLR-8339.patch
>
>
> Currently, both share a Map interface (SOLR-928). However, there are many
> common methods like createField(), setField() etc. that should perhaps go
> into an interface/abstract class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
