<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lucene index FULL recovery breaks record sorting in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260709#M213839</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Andy,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I will eventually have to upgrade to 4.0 but that would require too much work at this point, because I'm using the dod5015 module which is not supported yet in 4.0.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So far, we have a few workarounds left like supporting sorting on the client-side only (with YUI).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But to shade light on what is going on here, my understanding is that we should not do a full index recovery when using "EXACT_LANGUAGE_AND_ALL"?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because it would effectively break sorting?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The strange thing is that the cm:name property is still localized even after a full index recovery, so there must be some special treatment in this case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your explanation,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sylvain&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Feb 2012 15:43:49 GMT</pubDate>
    <dc:creator>sylvain78</dc:creator>
    <dc:date>2012-02-13T15:43:49Z</dc:date>
    <item>
      <title>Lucene index FULL recovery breaks record sorting</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260707#M213837</link>
      <description>Hi,I have a problem with sorting and I would like to have a few explanations regarding Lucene index, analysis modes and locales.Let's consider the following settings : Alfresco Community 3.4.dThe DOD5015 module is installed (so I can't move on to Solr yet)Server locale is en_USDefault analysis modes</description>
      <pubDate>Wed, 08 Feb 2012 16:56:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260707#M213837</guid>
      <dc:creator>sylvain78</dc:creator>
      <dc:date>2012-02-08T16:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Lucene index FULL recovery breaks record sorting</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260708#M213838</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can upgrade to 4.0 and still use lucene.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4.0 has a change to sort on &amp;lt;&amp;gt;.no_locale which will be better - but not as good as localized ordering with SOLR.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Feb 2012 10:24:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260708#M213838</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2012-02-13T10:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: Lucene index FULL recovery breaks record sorting</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260709#M213839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Andy,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I will eventually have to upgrade to 4.0 but that would require too much work at this point, because I'm using the dod5015 module which is not supported yet in 4.0.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So far, we have a few workarounds left like supporting sorting on the client-side only (with YUI).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But to shade light on what is going on here, my understanding is that we should not do a full index recovery when using "EXACT_LANGUAGE_AND_ALL"?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because it would effectively break sorting?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The strange thing is that the cm:name property is still localized even after a full index recovery, so there must be some special treatment in this case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your explanation,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sylvain&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Feb 2012 15:43:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-index-full-recovery-breaks-record-sorting/m-p/260709#M213839</guid>
      <dc:creator>sylvain78</dc:creator>
      <dc:date>2012-02-13T15:43:49Z</dc:date>
    </item>
  </channel>
</rss>

