aggregate 2.4.0 issue when using with split plugin about logstash-filter-aggregate

[fbaligand]

Actually, since version 2.4.0, if taskid pattern is not the same, aggregate map is not shared.
If you want sharing, you have to use the same taskid pattern so have to keep same value in same field name

[mrchang7]

Okay, I see. Then I will try to following the rule. It would be nicer to have that in the document. Currently, it says for the task_id, "This value must uniquely identify the task in the system."

Thanks for your quick help!

[fbaligand]

You are right.
I have to explain it in documentation.

That said, I truly think you should use version 2.3.1 :

• in this version, aggregate maps are nicely stored to configured path at shutdown
• and there is not this "new behavior" which annoy you.

[mrchang7]

As I made the patterns the same even with the field names, it worked as before. Can I ask why you made this change? Wondering.. the value of task_id should matter if the map keeps based on it.

Thanks!

[mrchang7]

The problem using 2.3.1 is we have multiple task_id's and like to set different time_out values to them.

[fbaligand]

To allow this new 2.4 feature (timeout options per task id pattern), I had to tie aggregate maps to their taskid pattern ; so that timeout management for one task id pattern process only associated aggregate maps.

[mrchang7]

That makes sense. Thanks!

[fbaligand]

@mrchang7
As it was a simple question, and the question is answered, could you close this issue ?