You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/11/01 07:50:00 UTC

[jira] [Commented] (NIFI-5777) Update the tag and the property of LogMessage

    [ https://issues.apache.org/jira/browse/NIFI-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671219#comment-16671219 ] 

Koji Kawamura commented on NIFI-5777:
-------------------------------------

I don't disagree about removing 'attributes' tag, but we need to be careful when we remove something already released. We can't guarantee that no one use 'attribute' tag to search that processor. I'd leave it as it is, if the benefit of doing so is relatively small.

As you guessed, if a property supports EL, it can not be a combo box, it needs to be a text input. I think there is an existing JIRA to improve that.

> Update the tag and the property of LogMessage
> ---------------------------------------------
>
>                 Key: NIFI-5777
>                 URL: https://issues.apache.org/jira/browse/NIFI-5777
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Kotaro Terada
>            Assignee: Kotaro Terada
>            Priority: Major
>
> There are a few points to update in {{LogMessage}}:
>  * The processor tags are a little bit strange. The current tags are "attributes" and "logging". A tag "attributes" is not suitable for this processor. I suggest just "logging" is enough.
>  * The property "Log Level" should be selected using a drop-down list (as it is done in {{LogAttribute}}). Currently, the field is just a text box, and users need to type a log level manually. If we set "expression language supported" on the property, does it force to make the property become a text field in the Web UI?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)