<?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: Advanced Lucene Search in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/advanced-lucene-search/m-p/204003#M157133</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I suspect this can't be expressed solely in Lucene (it's not as powerful a query language as SQL), but it could be implemented via a combination of Lucene (to find all images where P1="Large") and direct repository traversal (to find the parent folders of the set of images returned by the Lucene query).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Provided this is done in-process (eg. in a Web Script) this should be pretty performant, despite requiring N + 1 atomic operations (1 for the Lucene query + N for the directory lookups).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Jan 2009 05:50:09 GMT</pubDate>
    <dc:creator>pmonks</dc:creator>
    <dc:date>2009-01-03T05:50:09Z</dc:date>
    <item>
      <title>Advanced Lucene Search</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/advanced-lucene-search/m-p/204002#M157132</link>
      <description>So the problem we are tackling isL1&amp;nbsp;&amp;nbsp;&amp;nbsp; L2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; L3 &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; P1, P2, P3, P4 etc.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; P1, P2, P3, P4 etc.Where L1, L2, L3 are all folders and I1 in an image (instance) and P1, P2 P3 etc are all aspects. We are looking for a result set of all L3&amp;nbsp; where I* has som</description>
      <pubDate>Thu, 04 Dec 2008 07:21:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/advanced-lucene-search/m-p/204002#M157132</guid>
      <dc:creator>tpod2</dc:creator>
      <dc:date>2008-12-04T07:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Lucene Search</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/advanced-lucene-search/m-p/204003#M157133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I suspect this can't be expressed solely in Lucene (it's not as powerful a query language as SQL), but it could be implemented via a combination of Lucene (to find all images where P1="Large") and direct repository traversal (to find the parent folders of the set of images returned by the Lucene query).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Provided this is done in-process (eg. in a Web Script) this should be pretty performant, despite requiring N + 1 atomic operations (1 for the Lucene query + N for the directory lookups).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jan 2009 05:50:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/advanced-lucene-search/m-p/204003#M157133</guid>
      <dc:creator>pmonks</dc:creator>
      <dc:date>2009-01-03T05:50:09Z</dc:date>
    </item>
  </channel>
</rss>

