The deserializer interface does not restrict reads to lines. You can always write one that reads stack traces. If you end up writing one, we'd gladly review it to include it in flume itself.
On Saturday, May 9, 2015, Siva kotipalli <[email protected]> wrote: > Hi, > > The Spool directory source by default consider the carriage return as > event delimiter, when we have stack traces spread across more than one > line, they get stored as differnt events. > Do we have any plans for including MultilineDeserizer for Spool data > source, i created my own multiline deserializer used it via configuration, > but it would nice to have one included in the release. > > The same case as Tail datasource., where there is no option to include > multiple deserializer and i created my own custom source to support single > line and multiline log statements. > > The above queries are with reference to Flume 1.5.2 > > Thanks & Regards > Siva > -- Thanks, Hari
