lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yury Kartsev (JIRA)" <>
Subject [jira] [Created] (SOLR-9493) uniqueKey generation fails if content POSTed as "application/javabin".
Date Fri, 09 Sep 2016 17:26:20 GMT
Yury Kartsev created SOLR-9493:

             Summary: uniqueKey generation fails if content POSTed as "application/javabin".
                 Key: SOLR-9493
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Yury Kartsev

I have faced a weird issue when the same application code (using SolrJ) fails indexing a document
without a unique key (should be auto-generated by SOLR) in SolrCloud and succeeds indexing
it in standalone SOLR instance (or even in cloud mode, but from web interface of one of the
replicas). Difference is obviously only between clients (CloudSolrClient vs HttpSolrClient)
and SOLR URLs (Zokeeper hostname+port vs standalone SOLR instance hostname and port). Failure
is seen as "org.apache.solr.client.solrj.SolrServerException: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:
Document is missing mandatory uniqueKey field: id".

I am using SOLR 5.1. In cloud mode I have 1 shard and 3 replicas.

After lot of debugging and investigation (see my [StackOverflow post|])
I came to a conclusion that the difference in failing and succeeding calls is simply content
type of the POSTing requests. Local proxy clearly shows that the request fails if content
is sent as "application/javabin" (see attached) and succeeds if content sent as "application/xml;
charset=UTF-8"  (see attached).

Would you be able to please assist?

Thank you very much in advance!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message