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 2019/04/30 03:18:49 UTC

[GitHub] [pulsar] ConcurrencyPractitioner edited a comment on issue #4152: Allow PersistentTopics#updatePartitionedTopic to also delete partitions

ConcurrencyPractitioner edited a comment on issue #4152: Allow PersistentTopics#updatePartitionedTopic to also delete partitions
URL: https://github.com/apache/pulsar/issues/4152#issuecomment-487810087
 
 
   @sijie Oh, in that case, wouldn't we have to stop the flow of new records/messages into the ledgers? From my interpretation, from the approach you described, what we should do is basically stop all flow of new data from Producer to the partitions we wish to delete, finish processing the data that is still there, then delete them. 
   
   The most straightforward approach to deleting the partitions is as follows: if there was originally N partitions, and the user specifies us for K partitions, where K < N, we just delete the last N-K partitions (i.e. the ones with the biggest indexes). The partitions which are to be deleted I think would be made read-only once the user requests them to be deleted. 

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


With regards,
Apache Git Services