[GitHub] [druid] capistrant commented on pull request #10877: Allow coordinator to be configured to kill segments in future

[GitBox <gi...@apache.org>]

capistrant commented on pull request #10877:
URL: https://github.com/apache/druid/pull/10877#issuecomment-840111414


   > I have not read the change yet, but thought about what you've mentioned in the PR description.
   > 
   > What do you think of following a similar pattern to what we do for json config properties. Essentially, introduce a new config property with the new default of `PT0S`. And add code that validates the config that only one of the old and new property are set so that we can resolve this behavior. This way, operators can opt in to the functionality you're providing here without being forced to make a config change on an upgrade - just food for thought...
   > 
   > I will try to look into this over the next 2 weeks
   
   Hey suneet, reaching out to see if you've had a chance to think more about this proposed change since we last talked


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org