The stack trace is what gets returned to the client, right? It's often much more informative to see the Solr log output, the error message is often much more helpful there. By the time the exception bubbles up through the various layers vital information is sometimes not returned to the client in the error message.
One precaution I would take since you've changed the schema is to _completely_ remove the index. 1> shut down Solr 2> rm -rf coreX/data 3> restart Solr. 4> try it again. Lucene doesn't really care at all whether a field gets indexed one way in one document and another way in the next document and occasionally having fields indexed different ways (string and text) in different documents at the same time confuses things. Best, Erick On Thu, Jun 18, 2015 at 10:31 AM, Paden <rumsey...@gmail.com> wrote: > Just rolling out a little bit more information as it is coming. I changed the > field type in the schema to text_general and that didn't change a thing. > > Another thing is that it's consistently submitting/not submitting the same > documents. I will run over it one time and it won't index a set of > documents. When I clear the index and run the program again it > submits/doesn't submit the same documents. > > And it will index certain PDF's it just won't index others. Which is weird > because I printed the strings that are submitted to Solr and the ones that > get submitted are really similar to the ones that aren't submitted. > > I can't post the actual strings for sensitivity reasons. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Error-when-submitting-PDF-to-Solr-w-text-fields-using-SolrJ-tp4212704p4212757.html > Sent from the Solr - User mailing list archive at Nabble.com.
