<?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 path query performance in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265761#M218891</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Type queries are I think faster then the PATH queries.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have custom content type and want to search with that only better go for that as it straight away filter all other contents.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Also try changing the sequence of conditions as this will also affect the performance.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Feb 2012 13:43:10 GMT</pubDate>
    <dc:creator>mitpatoliya</dc:creator>
    <dc:date>2012-02-15T13:43:10Z</dc:date>
    <item>
      <title>Lucene path query performance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265759#M218889</link>
      <description>Hi,Is there any alternative for Path query in Lucene? We have a huge repository in which the documents are stored in hierarchical spaces and we want to search for a space in this hierarchy. The space that we search could be in any sub-folder under the root folder which we'll not know in advance. Hen</description>
      <pubDate>Tue, 29 Nov 2011 23:41:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265759#M218889</guid>
      <dc:creator>unknown-user</dc:creator>
      <dc:date>2011-11-29T23:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: Lucene path query performance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265760#M218890</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;Find you docs by some other way - an attribute tag (which you could manage using rules)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Move to 4.0 and SOLR in which PATH search is much faster.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jan 2012 10:00:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265760#M218890</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2012-01-13T10:00:08Z</dc:date>
    </item>
    <item>
      <title>Re: Lucene path query performance</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265761#M218891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Type queries are I think faster then the PATH queries.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have custom content type and want to search with that only better go for that as it straight away filter all other contents.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Also try changing the sequence of conditions as this will also affect the performance.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Feb 2012 13:43:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/lucene-path-query-performance/m-p/265761#M218891</guid>
      <dc:creator>mitpatoliya</dc:creator>
      <dc:date>2012-02-15T13:43:10Z</dc:date>
    </item>
  </channel>
</rss>

