You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2022/11/04 19:33:00 UTC

[jira] [Updated] (NIFI-10767) SyslogReader should not throw Exceptions on empty/blank lines

     [ https://issues.apache.org/jira/browse/NIFI-10767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-10767:
------------------------------
    Fix Version/s: 1.19.0
         Assignee: Mark Payne
           Status: Patch Available  (was: Open)

> SyslogReader should not throw Exceptions on empty/blank lines
> -------------------------------------------------------------
>
>                 Key: NIFI-10767
>                 URL: https://issues.apache.org/jira/browse/NIFI-10767
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.19.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If the SyslogReader encounters an empty line, it throws an Exception:
> {code:java}
> if (StringUtils.isBlank(line)) {
>     // while an empty string is an error
>     throw new MalformedRecordException("Encountered a blank message!");
> } {code}
> Often flows are built that use MergeContent or split data apart, etc. that can result in inadvertently including an empty line between messages. There's no need to throw an Exception in this case. Instead, we should simply skip over the empty line. Perhaps a debug log should be emitted but not an Exception.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)