<?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: Search Index in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Search-Index/m-p/1272302#M26184</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the online help file:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;The benefit of creating search index files during data reload is that you avoid the waiting time experienced by the first user making a search. This needs to be weighed against the longer data reload time required by search index creation.&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;So, have the choice. Precalculate the indexes or the first user to search gets to be the unlucky loser. &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Dec 2016 10:35:45 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2016-12-16T10:35:45Z</dc:date>
    <item>
      <title>Search Index</title>
      <link>https://community.qlik.com/t5/App-Development/Search-Index/m-p/1272301#M26183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We upgraded to Qlik Sense 3.1 and now our apps are indexed at the end of the reload.&lt;/P&gt;&lt;P&gt;I found out how to turn it off, but i was wondering what the benefits of the search index are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;I'm trying to make up my mind about turning it of or leaving it on. It does take a lot of extra time in some reloads, so that would be my reason to turn it off.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Does anyone know what the pro's are of using the search index?&lt;/P&gt;&lt;P&gt;What to you use it for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Isabelle&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2016 10:13:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Search-Index/m-p/1272301#M26183</guid>
      <dc:creator>ift_isabelle</dc:creator>
      <dc:date>2016-12-16T10:13:51Z</dc:date>
    </item>
    <item>
      <title>Re: Search Index</title>
      <link>https://community.qlik.com/t5/App-Development/Search-Index/m-p/1272302#M26184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the online help file:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;The benefit of creating search index files during data reload is that you avoid the waiting time experienced by the first user making a search. This needs to be weighed against the longer data reload time required by search index creation.&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;So, have the choice. Precalculate the indexes or the first user to search gets to be the unlucky loser. &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Dec 2016 10:35:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Search-Index/m-p/1272302#M26184</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2016-12-16T10:35:45Z</dc:date>
    </item>
  </channel>
</rss>

