[
https://issues.apache.org/jira/browse/SOLR-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929833#comment-17929833
]
David Smiley commented on SOLR-13731:
-------------------------------------
There are many classes in SolrJ and it's not always clear to us/users which
ones are internal, not to mention that in this case, we may disagree. I don't
see why a user using SolrJ would go out of their way to use JavaBinCodec as you
describe. Constructing a SolrInputDocument is easy :).
{{ConcurrentUpdateHttp2SolrClient}} streams updates.
> javabin must support a 1:1 mapping of the JSON update format
> -------------------------------------------------------------
>
> Key: SOLR-13731
> URL: https://issues.apache.org/jira/browse/SOLR-13731
> Project: Solr
> Issue Type: Task
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Fix For: 8.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Objects like SolrInputDocument is serialized in such a way that the size is
> known in advance. All objects should ideally support streaming friendly types.
> This is backward compatible . basically javabin will continue to serialize
> using the old format , but will accept more efficient formats as input
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
