RE: solr 1.3 Modification field in schema.xml
Hi Todd, Thanks for this answer, ok but it's not just showing or not in the list, if a field is not shown but it's boost using qf do I need to store it ??? For a language field which need some special configuration like stemming ... thanks a lot for your clear answer, I believe (someone correct me if I'm wrong) that the only fields you need to store are those fields which you wish returned from the query. In other words, if you will never put the field on the list of fields (fl) to return, there is no need to store it. It would be advantageous not to store more then you have to. It reduces disk access, index size, memory usage, etc. However, you have to balance this against future needs. If re-indexing is costly just to start storing 1 more field, it may be worth it to just leave it in. -Todd Feak -- View this message in context: http://www.nabble.com/solr-1.3--Modification-field-in-schema.xml-tp20483691p20536926.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr 1.3 Modification field in schema.xml
On Thu, Nov 13, 2008 at 10:43 PM, sunnyfr [EMAIL PROTECTED] wrote: Hi everybody, I don't get really when do I have to re index datas or not. I did a full import but I realised I stored too many fields which I don't need. So I have to change some fields inedexed which are stored to not stored. And I don't know if I have to re index my datas or not and in which case really do I have to re index datas. You will have to re-index Another question, I would like to know which field must be stored, I thought it was field which use function for boosting, but I just tried to boost one field indexed but not stored and it worked. Thanks a lot for putting some light on my questions, -- View this message in context: http://www.nabble.com/solr-1.3--Modification-field-in-schema.xml-tp20483691p20483691.html Sent from the Solr - User mailing list archive at Nabble.com. -- --Noble Paul
RE: solr 1.3 Modification field in schema.xml
I believe (someone correct me if I'm wrong) that the only fields you need to store are those fields which you wish returned from the query. In other words, if you will never put the field on the list of fields (fl) to return, there is no need to store it. It would be advantageous not to store more then you have to. It reduces disk access, index size, memory usage, etc. However, you have to balance this against future needs. If re-indexing is costly just to start storing 1 more field, it may be worth it to just leave it in. -Todd Feak -Original Message- From: sunnyfr [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2008 9:13 AM To: solr-user@lucene.apache.org Subject: solr 1.3 Modification field in schema.xml Hi everybody, I don't get really when do I have to re index datas or not. I did a full import but I realised I stored too many fields which I don't need. So I have to change some fields inedexed which are stored to not stored. And I don't know if I have to re index my datas or not and in which case really do I have to re index datas. Another question, I would like to know which field must be stored, I thought it was field which use function for boosting, but I just tried to boost one field indexed but not stored and it worked. Thanks a lot for putting some light on my questions, -- View this message in context: http://www.nabble.com/solr-1.3--Modification-field-in-schema.xml-tp20483 691p20483691.html Sent from the Solr - User mailing list archive at Nabble.com.
