Search results exceed set_result_set_limit
- Article Type: General
- Product: Aleph
- Product Version: 16.02
Description:
In our v16 www_server.conf we have:.
setenv set_result_set_limit 5000.
But I just did a WRD search for history, and retrieved over 300,000 records, sorted!
Resolution:
In the "Records 1-xx of nnnnn", the "nnnnn" represents the total number of hits. The system does not build a result-set entry for every hit. It stops when it reaches the set_result_set_limit. In your case, with set_result_set_limit 5000 and set_default_z110_create_order "D", it has taken the 5,000 highest-numbered results and sorted them. If you were to continue paging through the results you would see that they stop at 5000..
The distributed ./www_f_eng/short-include-2 has: "Records $0100 -$0200 of $0300 (maximum display and sort is $4500 records)". In this structure the $4500 is the set_result_set_limit.
- Article last edited: 10/8/2013