[
https://issues.apache.org/jira/browse/SOLR-10637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021993#comment-16021993
]
Hoss Man commented on SOLR-10637:
---------------------------------
bq. No problem. Unfortunately, my IRC session was closed accidentally and I
lost the comments that Chris and elyograg had made on this issue. So I could
not add them here. But, the core issue is basically what I have mentioned in
the description.
In a nutshell:
* I concurred that the reasons given in SOLR-8339 for why the method should be
deprecated make no sense to me because i didn't see any way the refactoring
solved the same use case as the method.
* I cautioned that in general, converting from SolrDocument to
SolrInputDocument isn''t always safe from a client perspective because of
non-stored fields
Personally: Even though i don't think the reasons given for removing it make
any sense, I'm not convinced this usage pattern is something should be
encouraging by adding this functionality back to any public solrj method ...
ie: +0.
> org.apache.solr.client.solrj.util.ClientUtils.toSolrInputDocument is removed
> in Solr 6.0 and there is no alternative
> --------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-10637
> URL: https://issues.apache.org/jira/browse/SOLR-10637
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.0
> Reporter: A Bronley
> Priority: Minor
> Attachments: SOLR-10637.patch
>
>
> There is no subtitute available now to convert SolrDocument to
> SolrInputDocument because
> org.apache.solr.client.solrj.util.ClientUtils.toSolrInputDocument is removed
> in Solr 6.0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
