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

ASF GitHub Bot commented on ARTEMIS-1951:
-----------------------------------------

GitHub user michaelandrepearce opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2161

    ARTEMIS-1951 allow queue's user to be updated

    Fix so that it only updates if not null, to avoid user being unset from 
existing api's, 
    This is similar to other values, that only change the value when not null.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/michaelandrepearce/activemq-artemis 
ARTEMIS-1951

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2161.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2161
    
----
commit 7c35fc5ef89f084e6bcbe551f35216a65ba3ae27
Author: Michael André Pearce <michael.andre.pearce@...>
Date:   2018-06-25T12:55:16Z

    ARTEMIS-1951 allow queue's user to be updated
    
    Fix so that it only updates if not null, to avoid user being unset from 
existing api's, 
    This is similar to other values, that only change the value when not null.

----


> Queue's user can't be updated
> -----------------------------
>
>                 Key: ARTEMIS-1951
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1951
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.7.0
>
>
> ARTEMIS-1569 added the ability to specify the queue's user via XML.  However, 
> the user set on the XML when the queue is first created can never be changed 
> later.



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

Reply via email to