sumitagrawl commented on PR #7326: URL: https://github.com/apache/ozone/pull/7326#issuecomment-2427209692
> > OM 1.4.x cannot report it is at OzoneManagerVersion = 5: that would fool newer clients to believe OBJECT_TAG(5) is supported. So it must keep reporting version = 4. If client only looks at OM version, it cannot distinguish between 1.4.0 and 1.4.1+ OM. > > Therefore, whether we set `LIGHTWEIGHT_LIST_STATUS` to version 4 or version 5, there will be compatibility issues. If Server and client is already upgraded to `1.4.0` and `LIGHTWEIGHT_LIST_STATUS` feature is already present, then there is no useful of adding that check explicitly now. For specific compatibility fix, a client of 1.4.1 can take a decision if there is a failure, fall back to older way as that client specific code for compatibility. Bitwise map of feature -- - it will be complex to manage master feature, sub-branch release if its implemented with conflicting index, chance of misuse is there. - This is rare case of conflict, and if any such case happens, a specific code is better to manage for that client version. IMO, keeping versioning simple will help reduce complexity of getting bigger issue later on. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
