Each core has a different database as a datasource, which means that they have different DB structures and fields. That is why the schemas are different.
I figured out the cause of this problem. You were right, it was the uniqueKey field. All of my cores have that field set to "id" but for this new core, it is set to "threadID". Changing that to id fixed the problem. Shalin Shekhar Mangar wrote: > > On Tue, Aug 18, 2009 at 9:01 PM, ahammad <ahmed.ham...@gmail.com> wrote: > >> HTTP Status 500 - null java.lang.NullPointerException at >> >> org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:437) >> at >> >> The way I created this shard was to copy an existing one, erasing all the >> data files/folders, and modifying my schema/data-config files. So the >> core >> settings are pretty much the same. >> > > What did you modify in the schema? All the shards should have the same > schema. That exception can come if the uniqueKey is missing/null. > > If all the shards should have the same schema, then what is the point of > sharding in the first place? I thought that it was used to combine > different cores with different index structures...Right now, every core I > have is unique, and every schema is different... > > -- > Regards, > Shalin Shekhar Mangar. > > -- View this message in context: http://www.nabble.com/Strange-error-with-shards-tp25027486p25043859.html Sent from the Solr - User mailing list archive at Nabble.com.
