I am using this CreateSearchIndexonReload attribute in my application. I have never faced the issue in past but recently my reload always fails during index creation only. Data reload is however successful after disabling this. I am wondering what might be the reason.
The only difference with the current and previous version is that the previous version was just loaded as is and had numerous synthetic keys on it. But in the current version, I have changed the model with linktable and auto-numbered keys.
Please help me understand the reason for failure in creating search index.
We experienced the same issue with one of our applications, the following article guided us: CreateSearchIndexOnReload;
You will find this parameter initialized to 1 (yes) in the Data Load Script of the offending application(s), just turn it off, and it will reload, even faster, if you read the article above, that index is required when you perform searches on the User Interface, we haven't experience any issue since turning it off on the applications returning the error when reloading.
Hope this helps,
We did the same, I am just waiting for some of the member of the Qlik Community to explains further or for us to do some research on this issue, but we do not have time for the research at the moment.
I too came across this failure. The reload has got stuck when creating the search index and it happens frequently. Can anyone explain me from technical perspective that what is the reason behind and what will be the impact if we disable it?
As stated above, you can turn off this feature and give a try on your reload.
While the technical reason for such failure is not known, I can explain the nuances behind CreateSearchIndexOnReload.
This parameter when enabled instructs Qlik to build indexes for the various fields once reload is complete.
Disabling this would not cause any impact to reload process. It is just that the first search you do using the search option on the UI would take an additional overhead of building indexes at the runtime, which might be even negligible depending on your application.
Hope this helps!
Thanks! Just wondering how this could cause the reload task to hang. Seems like this operation will not require much memory. The task completing refresh successfully some times and hung some times at this line.