[ 
https://issues.apache.org/jira/browse/ARTEMIS-2797?focusedWorklogId=455178&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-455178
 ]

ASF GitHub Bot logged work on ARTEMIS-2797:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Jul/20 01:37
            Start Date: 07/Jul/20 01:37
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on pull request #3213:
URL: https://github.com/apache/activemq-artemis/pull/3213#issuecomment-654547763


   @jsmucr Why such semantic change regarding updateQueue? that's a contract 
break on the API.. and a big semantic change.
   
   As a matter of fact those testRemoteQueueFilter stopped working because of 
this.
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 455178)
    Time Spent: 6h 50m  (was: 6h 40m)

> Reset queue properties by unsetting them in broker.xml
> ------------------------------------------------------
>
>                 Key: ARTEMIS-2797
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2797
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.13.0
>            Reporter: Jan Å mucr
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.14.0
>
>          Time Spent: 6h 50m
>  Remaining Estimate: 0h
>
> Currently the queue properties cannot be removed because of property new 
> value null checks leading to quitting the PostOfficeImpl#updateQueue() 
> instead of resetting the properties to their default values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to