ok, i'm starting to see the light :)) at this moment, we are running this for our uniqueID : field : <field name="id" type="idstring" stored="true"/> and everything is working well ...
so i dont explicitly say indexed='true' ... i guess indexed is default true ... i'll be sure do to do some testing with stored=false and indexed=false but that'll be for next week when i start optimizing i'll be sure to mail you the results of the testing thanks again,m Chris Hostetter <[EMAIL PROTECTED]> 19/03/2007 20:30 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org cc Subject Re: Bug ? unique id : it would maybe be a good idea to have Lucene check the *stored* value for : duplicate keys ... that seems so much more logical to me ! : (imho, it makes no sense to check the *indexed* value for duplicate keys, : but maybe there is a reason ?) it's probably a terminology issue ... stored fields are nothing more then Payloads .. LUcene (and Solr) don't do anything with them but hang on to them for you and return them to you later. the "indexed" value is the value that matters in the "index" ... it's the one searches/lookups and sorting can be performed on. : or maybe give us the option to choose wether Lucene should check the : *stored* or *indexed* value for duplicate keys. if Solr were to try and deal with your uniqueKey using hte Stored value, it would have to do the same copyField stuff under the coveres in order for that Stored value to be "indexed" in a way it can see it. : since we now use a copyfield to perform searches on the IDs, there is no : more reason to index our unique key field .... : what would happen if I set indexed=false on my unique id field ?? it wouldn't work at all ... as i said, the indexed value is all that Solr really cares about -- i think you could probably mark your uniqueKey as stored=false, but if it's indexed-false then at best you'll get a nice error telling you it must be indexed, and at worst it will crash and burn in a non-obvious way -- possibly silently. (if you want to try it out, and the later happens, please file abug we should definitely have a nice error message in that case) -Hoss
