You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/12/04 20:32:11 UTC

[jira] [Commented] (NIFI-1254) GetJMSQueue and GetJMSTopic have unnecessary Destination Type property

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

Mark Payne commented on NIFI-1254:
----------------------------------

Agreed - that should certainly not be there. Thanks for pointing this out, Mike!

> GetJMSQueue and GetJMSTopic have unnecessary Destination Type property
> ----------------------------------------------------------------------
>
>                 Key: NIFI-1254
>                 URL: https://issues.apache.org/jira/browse/NIFI-1254
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Michael Moser
>            Assignee: Michael Moser
>             Fix For: 0.4.0
>
>         Attachments: 0001-NIFI-1254.patch
>
>
> GetJMSQueue and GetJMSTopic have added a new property Destination Type.  The values for Destination Type are "Queue" and "Topic". Testing with the latest code in master, the Destination Type property doesn't seem to have any affect on the processor, since GetJMSQueue with Destination Type = Topic still reads from a queue (and vice versa).
> Destination Type property was not in the 0.3.0 release.  Remove the new Destination Type property before the 0.4.0 release.  It gets very inconvenient to remove properties after a release, because you would get "Destination Type is not a supported property" warnings if you keep the same flow.xml when you upgrade to a new NiFi release.
> I'm testing a patch ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)