[
https://issues.apache.org/jira/browse/NIFI-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110059#comment-15110059
]
Joseph Witt commented on NIFI-1139:
-----------------------------------
moved off 050. I agree we should not be drawing a distinction in how we refer
to flow file attributes. All of its 'things' are attributes. Some attributes
are always there and of a specific type. That we can document. But I think
the current log output is correct.
> logAttribute processor output incorrectly identifies FlowFile properties as
> FlowFile attributes.
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1139
> URL: https://issues.apache.org/jira/browse/NIFI-1139
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Matthew Clarke
> Assignee: Oleg Zhurakousky
> Priority: Minor
>
> There are certain pieces of a FlowFile that are not attributes (entryDate,
> lineageDate, and fileSize); howwver, the output from a logAttribute processor
> identifies them as FlowFile attributes. These items should be labeled as
> FlowFile properties.
> --------------------------------------------------
> Standard FlowFile Attributes
> Key: 'entryDate'
> Value: 'Tue Nov 10 09:02:01 EST 2015'
> Key: 'lineageStartDate'
> Value: 'Tue Nov 10 09:02:01 EST 2015'
> Key: 'fileSize'
> Value: '10240'
> FlowFile Attribute Map Content
> Key: 'divideby3'
> Value: '-7'
> Key: 'divideby5'
> .....
> ----------------------------------------------------------
> Need to change the output wording:
> "Standard FlowFile Attributes" should be "Standard FlowFile Properties"
> I also think uuid should be included under this section.
> We want to avoid confusion for the users. All Attributes are stored as
> strings. Properties are not attributes and are not stored as strings. That
> distinction directly correlates to how the expression language can interact
> with these values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
