[
https://issues.apache.org/jira/browse/SOLR-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258252#comment-13258252
]
Jan Høydahl commented on SOLR-3038:
-----------------------------------
Doesn't matter. One customer of ours use an ECM system with built-in Solr1.x
for internal search. This ECM is a Java webapp, and the publications run in the
same app, so that our JARs must live in harmony with theirs. We use SolrJ for
searching an external 3.5 search cluster, but since we can have only one SolrJ
on the classpath of the webapp, it must be one which can talk to both the 1.x
internal solr instance and our 3.x external one. That excludes JavaBin because
of incompat. We have first been using solr-solrj-1.4.1.jar in XML mode and now
solr-solrj-3.5.0.jar in XML mode, which is still compatible.
> Solrj should use javabin wireformat by default with updaterequests
> ------------------------------------------------------------------
>
> Key: SOLR-3038
> URL: https://issues.apache.org/jira/browse/SOLR-3038
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 4.0
> Reporter: Sami Siren
> Priority: Minor
>
> The javabin wire format is faster than xml when feeding Solr - it should
> become the default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
