jinmeiliao commented on pull request #5879: URL: https://github.com/apache/geode/pull/5879#issuecomment-755507388
As far as I know, we rarely do multi-property cross validation at startup, i.e, we don't check if property A is set then property B can't be set. Initial validation is usually based on one property only (i.e integer is between a number and string is only a certain values etc.). Multi-property conflict is usually handled by ignoring one property (if A is set, then B has no effect). I wonder if we should take this route instead. ---------------------------------------------------------------- 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]
