Changes of Exalead in GN4 version 1.4

Build 1501 on 14/Nov/2017  This topic last edited on: 13/Sep/2015, at 15:00

Added Exalead support for boolean attributes. Boolean attributes are now indexed as 0/1. Added Exalead search templates for boolean: ExaleadRadio, ExaleadCheckbox. Added support to ExaleadCheckBoxList, ExaleadCompactList, ExaledSingle, ExaleadListBox templates when searching for enumeration attributes.

There is now a time-out for full-text index commit operations. Before this changes the system waited for Exalead to complete a full-text index commit without any time limit, i.e. possibly forever. The time-out is defined in the "Exalead" element of "ServerConfig" by two new parameters "CommitTimeoutBase" and "CommitTimeoutPerObject":

<Exalead

BaseCommandUrlV5="http://localhost:10010/search-api/search" 

BasePapiServerUrlV5="http://localhost:10002" 

ShowRefinements="true" 

CommitTimeoutBase="10000" 

CommitTimeoutPerObject="50"/> 

Both parameters are expressed in milliseconds. The total time-out time for a commit operation is "CommitTimeoutBase" plus "CommitTimeoutPerObject" times the number of objects being indexed. Their default values are 120000 (120 seconds = 2 minutes) and 250 respectively.

For example using the default values the time-out when indexing 500 objects is 120000+250*500 = 245000 = 245 seconds = around 4 minutes.

If a full-text index commit does not complete wihin the specified time-out the system logs (or displays) an error:

Exalead index commit failed: exceeded the XX seconds time-out 

where XX is the computed time-out.

When requesting just a full-text index commit using:

srv4 commitindex 

the system uses 100,000 as the number of objects to compute the time-out.

The time-out applies only to Exalead version 5.x (CloudView), not to the previous versions 4.x.

Added the ExaleadTags workflow activity that uses Exalead to extract tags from a list of objects, returning them as XML.