Getting Data In

Impact of LineBreakingProcessor and AggregateMiningProcessor on indexing performance


When indexing a directory containing html files, log files, zipped log files and gzipped log files, I am getting many LineBreakingProcessor and AggregateMiningProcessor warnings. It is scattered with them.
LineBreakingProcessor: When a line exceepds a predefined lenght (default 10,000bytes)
AggregateMiningProcessor: When an event has more than 256 lines.

Can someone please elaborate more on the performance impact of these?

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!