The cleanest is to do this from the outside. Alternatively, it will perhaps work to populate your uniqueKey in a custom UpdateProcessor. You can try.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 28. mai 2013 kl. 17:12 skrev Rishi Easwaran <rishi.easwa...@aol.com>: > Hi All, > > Historically we have used a single field in our schema as a uniqueKey. > > <field name="docid" type="string" indexed="true" stored="true" > multiValued="false" required="true"/> > <field name="userid" type="string" indexed="true" stored="true" > multiValued="false" required="true"/> > <uniqueKey>docid</uniqueKey> > > Wanted to change this to a composite key something like > <uniqueKey>userid-docid</uniqueKey>. > I know I can auto generate compositekey at document insert time, using custom > code to generate a new field, but wanted to know if there was an inbuilt SOLR > mechanism of doing this. That would prevent us from creating and storing an > extra field. > > Thanks, > > Rishi. > > > >
