[
https://issues.apache.org/jira/browse/NIFI-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988172#comment-15988172
]
Joseph Witt commented on NIFI-3758:
-----------------------------------
[~trixpan] I think we should consider letting these processors go away and
instead add ListenSyslogRecord (or update the old one to this) and it would
read them in and serialize them using the new record stuff. We can have the
schema we want to honor be a default value property on the processor and then
the data can be made readily parsed/usable/querable in the flow all with very
high throughput, configurability, and provenance. Probably not a 1.2 thing in
terms of timeframe but we really need to get in the habit of releasing more
often anyway!
> Allow users to not add message as attribute when using ParseSyslog and
> ListenSyslog
> ------------------------------------------------------------------------------------
>
> Key: NIFI-3758
> URL: https://issues.apache.org/jira/browse/NIFI-3758
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Andre F de Miranda
>
> [~bbende] - not sure if you agree with me, but it would be great if
> ListenSyslog and ParseSyslog had the ability of NOT adding the syslog
> {{message}} field to the flowfile attributes.
> Rationale is that while several attributes such as priority, facility, etc
> are very handy for routing decisions, the {{message}} field may contain an
> arbitrary volume of data that may better left as flowfile content.
> Happy to try to tackle this quickly so we include into 1.2.0 :-P
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
