topic Re: Lucene Index Erosion in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221908#M175038 <HTML><HEAD></HEAD><BODY><SPAN>You are my hero! we struggled for 2 weeks with this search problem, with your advice everything seems to work fine</SPAN></BODY></HTML> Fri, 28 May 2010 09:09:39 GMT spanishjohnny 2010-05-28T09:09:39Z Lucene Index Erosion https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221906#M175036 I have worked for 1 years with Alfresco Labs 3.0 and I had problems several times with the outcome of the Lucene search engine. Quite clearly the problems were found in an expansion around a new store to light. Some content usage information, which was stored in a separate store, was not found prope Thu, 22 Oct 2009 09:50:28 GMT https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221906#M175036 dbachem 2009-10-22T09:50:28Z Re: Lucene Index Erosion https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221907#M175037 <HTML><HEAD></HEAD><BODY><SPAN>So, since nobody gave any reply to this, i must reply to the public myself. Maybe this helps some of you who try to get along with multilingual content - as we do:</SPAN><BR /><BR /><UL><LI>we are dealing with content in different languages (german, english, italian, spanish)</LI><BR /><LI>not only the content, but also metadata (like cm:summary) are localized to different languages</LI><BR /><LI>this evokes usage of different analyzers, as defined with WEB-INF/classes/alfresco/model/dataTypeAnalyzers_??.properties</LI><BR /><LI>the AlfrescoStandardAnalyser (used for english content) doesn't use stemming, but other language-specific analyzers do!</LI><BR /><LI>this means, that <STRONG>all</STRONG> tokenised properties of nodes which are localized to german are transformed by the GermanAnalyzer</LI><BR /><LI>in other words: "cm:creator", "cm:modifier" and all other properties of d:text and d:content will be stemmed by a german stemmer!!</LI></UL><SPAN>And this causes, that for german content in the lucene index, admin will become "admi", meanwhile for english content it will remain "admin". And you won't be able to successfully search for "@cm\:creator:"admin" over german and english content in one query! Cause the query terms itself will be localized to one (and only one) language, so whether will be stemmed (query localized to german) or not (english).</SPAN><BR /><BR /><SPAN> :idea:&nbsp; From my point of view, the only solution for this problem is to change from language-specific analysers to the AlfrescoStandardAnalyser.</SPAN><BR /><BR /><SPAN>If some of you have any ideas, pls let me know!&nbsp; </SPAN><BR /><SPAN>Kind regards, Dirk</SPAN></BODY></HTML> Tue, 10 Nov 2009 14:29:04 GMT https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221907#M175037 dbachem 2009-11-10T14:29:04Z Re: Lucene Index Erosion https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221908#M175038 <HTML><HEAD></HEAD><BODY><SPAN>You are my hero! we struggled for 2 weeks with this search problem, with your advice everything seems to work fine</SPAN></BODY></HTML> Fri, 28 May 2010 09:09:39 GMT https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221908#M175038 spanishjohnny 2010-05-28T09:09:39Z Re: Lucene Index Erosion https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221909#M175039 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>I did the same and it seems to work as I expect.</SPAN><BR /><BR /><SPAN>Regards.</SPAN></BODY></HTML> Fri, 09 Jul 2010 17:15:42 GMT https://connect.hyland.com/t5/alfresco-archive/lucene-index-erosion/m-p/221909#M175039 roberto_negrete 2010-07-09T17:15:42Z