which yields different results on 1.5.16--build-6312 and 1.5.23--build-6794.
The function collect should collect the values of the fields alert.signature_id and alert.signature, and the collected result should be of length total_count for each alert.category of the result entries.
The problem is that on 1.5.23--build-6794, collection is terminated when the length of the rawstring exceeds the limit, but not on 1.5.16--build-6312. Setting maxlen=2000000 instead of the default 2000 fixes the issue and yields the same results on both versions. My opinion is that all the fields should be collected regardless of the value of maxlen (as in 1.5.16), or at least when there is a drop(@rawstring). Optionally, an option to disable collection into a rawstring could be added, thus resolving the entire issue.
I have the following query:
which yields different results on 1.5.16--build-6312 and 1.5.23--build-6794. The function collect should collect the values of the fields
alert.signature_id
andalert.signature
, and the collected result should be of lengthtotal_count
for eachalert.category
of the result entries. The problem is that on 1.5.23--build-6794, collection is terminated when the length of the rawstring exceeds the limit, but not on 1.5.16--build-6312. Settingmaxlen=2000000
instead of the default 2000 fixes the issue and yields the same results on both versions. My opinion is that all the fields should be collected regardless of the value of maxlen (as in 1.5.16), or at least when there is adrop(@rawstring)
. Optionally, an option to disable collection into a rawstring could be added, thus resolving the entire issue.