joshelser commented on pull request #1722: URL: https://github.com/apache/hbase/pull/1722#issuecomment-630272816
> I wonder if this should actually be enabled by default, as can't think why one would want to get replication stuck on Tables/CFs that had been removed on both source and target. I agree with you that failing all replication when the tables/cf's don't match is a smell. However, I have a concern that we don't have enough insight into when we would start dropping data to replicate onto the floor because of such a mismatch. I think we would need an observability improvement to turn this on by default (something to clearly say -- "your data is being dropped"). ---------------------------------------------------------------- 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: [email protected]
