You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/10/28 16:19:47 UTC

[GitHub] [pulsar] lhotari commented on pull request #8397: [Issue 7372][docs] Add detailed info for retention policy

lhotari commented on pull request #8397:
URL: https://github.com/apache/pulsar/pull/8397#issuecomment-718046439


   > And is the 0-value treated as a special value?
   
   @ErikJansenIRefact 
   Yes, `0` is a special value. Setting either limit to `0` will disable retention. That's the catch. 
   PR #8358 introduced new behavior that prevents setting just one of the values to 0 via the Admin API. To disable the retention policy, both values have to be set to 0 when using the Admin API. 
   The "setting either limit to 0 will disable retention" behavior still applies to existing configurations (after upgrading to 2.7.0 when it's out) and also for `defaultRetentionTimeInMinutes` and `defaultRetentionSizeInMB` settings. I wonder how to get this documented?


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