: Sorry, schema.xml file is here in this mail... in the schema.xml file you attached, the uniqueKey field is "evid"
you only provided one example of the type of input you are indexing, and in that example... : > <field name="evid">501</field> ...but in your orriginal email (see below) you said you were using a timestamp field as the uniqueKey, and you didn't understand why reindexing hte same 100 docs twice didn't give you 200 docs. that example uniqueKey value isn't a timestamp, so i don't really understand what you're talking about. if you index that doc over and over with the schema.xml you sent, then it's constaintly going to replace it self over and over again because hte uniqueKey field (evid) is the same (501) everytime. : > > : Here, i specified 20 fields in schema.xml file. the unoque field i set : > > was, : > > : currentTimeStamp field. : > > : So, when i run the loader program (which loads xml data into solr) it : > > creates : > > : currentTimestamp value...and loads into solr. : > > : : For this situation, : > > : i stopped the loader program, after 100 records indexed into solr. : > > : Then again, i run the loader program for the SAME 100 records to indexed : > > : means, : > > : the solr results 100, rather than 200. : > > : : Because, i set currentTimeStamp field as uniqueField. So i expect the : > > result : > > : as 200, if i run again the same 100 records... : > > : : Any suggestions please... -Hoss
