lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AJ Lemke <>
Subject RE: String Cast Error
Date Wed, 26 Mar 2014 19:55:59 GMT
An update to this.
If I change my search and add a parameter the error seems to go away.

/solr/collection1/select?q=*:* &wt=json&sort=inStock desc

No Error:
/solr/collection1/select?q=Samsung&wt=json&sort=inStock desc


-----Original Message-----
From: AJ Lemke [] 
Sent: Tuesday, March 18, 2014 5:28 PM
Subject: RE: String Cast Error

Did you change the schema at all?

Did you upgrade Solr from a previous version with the same index?

This was fresh install from the website.
Ran "ant run-example" 
Killed that instance
Copied Example to Node1
Copied Example to Node2
Switched into Node1
java -Dbootstrap_confdir=solr/collection1/conf -Dcollection.configName=collection1 -DzkRun
-DnumShards=2 -jar start.jar

Switched into Node2
java -Djetty.port=7574 -DzkRun -DzkHost=localhost:9983 -jar start.jar

Added documents using the following:
Switched into example/exampledocs
java -Dtype=text/xml -jar post.jar *.xml java -Dtype=text/csv -jar post.jar *.csv java -Dtype=application/json
-jar post.jar *.json

If you need more info let me know.


-----Original Message-----
From: Shawn Heisey []
Sent: Tuesday, March 18, 2014 5:14 PM
Subject: Re: String Cast Error

On 3/18/2014 3:51 PM, AJ Lemke wrote:
> I have a strange issue with my local SOLR install.
> I have a search that sorts on a boolean field. This search is pulling the following error:
"java.lang.String cannot be cast to org.apache.lucene.util.BytesRef".
> The search is over the dummy data that is included in the exampledocs.  I am searching
on a 2 node, 2 shard environment.
> I have included what I think is the pertinent information below.
> Thanks for any insights

Info gathering questions:

Did you change the schema at all?  If so, did you reindex? A reindex is required for virtually
all schema changes.

Did you upgrade Solr from a previous version with the same index?Solr is supposed to handle
this with no problems.

If you did ugprade Solr, whether the index was rebuilt or not, there may be leftover components
from the previous war extraction.  It looks like you're using the example jetty included with
Solr, so this would apply: 
It's best to delete anything in the solr-webapp directory for each upgrade.  You also want
to be sure that you don't have old jars hanging around in your classpath.

You could be running into a bug that I don't know about yet, but we can't assume that's the
case without ruling other problems out.


View raw message