Hi!!! I have already realized the mistake.My "id" field was generated from the copy of another field called "url".In other words....
<copyField source="url" dest="id"/> It seems that the thing did not work well when the "id" field was generated from the copy of another one. Now I have changed the schema.xml so that this does not happen. <field name="id" type="string" indexed="true" stored="true" required="true"/> so the documents indexed for the first time have to contain the id field. Thank you very much for your attention !!! Regards... Koji Sekiguchi-2 wrote: > > I've just tried this again in my environment, but I couldn't reproduce > what you pointed. > > My schema is: > > : > <field name="id" type="string" indexed="true" stored="true" > required="true" /> > <field name="name" type="text" indexed="true" stored="true"/> > <field name="tags" type="text" indexed="true" stored="true" > multiValued="true"/> > : > <uniqueKey>id</uniqueKey> > > > Koji > > > nutchvf wrote: >> Hi!! >> Thank you very much,Koji!! >> Your response has helped me a lot and I have already managed to update >> the >> document.Now,I have another problem: >> Sending the update request to Solr: >> >> For example: >> http://localhost:8389/solr/update?mode=tags:overwrite&commit=true >> >> <add> >> <doc> >> <field name="id">AAA</field> >> <field name="tags">German</field> >> </doc> >> </add> >> >> After that step,I realized that the "id" field,(defined in my schema.xml >> as >> an uniqueKey field) appears as a multivalued field,with two "fields" with >> the same value.Do you know which may be the reason for this behavior? >> >> Thank you, >> >> Regards! >> >> > > > -- View this message in context: http://www.nabble.com/Updating-in-Solr.SOLR-139-tp16744841p16892573.html Sent from the Solr - User mailing list archive at Nabble.com.
