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

ASF GitHub Bot commented on GEODE-7458:
---------------------------------------

DonalEvans commented on pull request #5223:
URL: https://github.com/apache/geode/pull/5223#issuecomment-641496854


   > Hi,
   > 
   > this is not good practice, that due to your internal test, which are not 
part of the community,
   > commit is reverted.
   > I think that you need first, to push problematic test case to community, 
then we can revert commit.
   
   You're correct, this is not best practice. I will close this PR until we are 
able to provide you with a test to reproduce the issue.


----------------------------------------------------------------
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


> Adding additional option in gfsh command  "start gateway sender" to control 
> clearing of existing queues
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7458
>                 URL: https://issues.apache.org/jira/browse/GEODE-7458
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs, wan
>            Reporter: Mario Ivanac
>            Assignee: Mario Ivanac
>            Priority: Major
>              Labels: needs-review, pull-request-available
>             Fix For: 1.14.0
>
>          Time Spent: 13h 20m
>  Remaining Estimate: 0h
>
> We would like to add additional option in gfsh command  "start gateway sender"
>  to control clearing of existing queues --cleanQueues.
>  
>  This option will indicate, when gateway sender is started, should we 
> discard/clean existing queue, or should we use existing queue.
>  
>  



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

Reply via email to