[
https://issues.apache.org/jira/browse/SOLR-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781483#comment-13781483
]
Mark Miller commented on SOLR-3530:
-----------------------------------
This is the root cause of the infamous "Invalid version (expected 2, but 60) or
the data in not in 'javabin' format". I saw some of this while working on
SOLR-5291 and am taking a stab at it as part of that issues patch.
> better error messages / Content-Type validation in solrJ
> --------------------------------------------------------
>
> Key: SOLR-3530
> URL: https://issues.apache.org/jira/browse/SOLR-3530
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Mark Miller
>
> spin off from SOLR-3258, it would be helpful if SolrJ, when encountering
> Exceptions from the ResponseParser (or perhaps before ever even handing data
> to the ResponseParser) did some validation of the Content-Type returned by
> the remote server to give better error messages in cases where miss
> configuration has the wrong matchup between ResponseParser and mime-type (or
> worse: an HTML page being returned by a non-solr server)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
