adoroszlai opened a new pull request, #11311: URL: https://github.com/apache/ozone/pull/11311
## What changes were proposed in this pull request? `repro` check started [failing](https://github.com/apache/ozone/actions/runs/35729886542/job/106757753923#step:14:4660) intermittently after bumping server-side Java version to 17. The root cause is variable ordering of items in `permits` list of some enums: ``` ├── org/apache/hadoop/ozone/om/request/validation/ValidationCondition.class │ ├── procyon -ec {} │ │ @@ -1,13 +1,13 @@ │ │ │ │ package org.apache.hadoop.ozone.om.request.validation; │ │ │ │ import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos; │ │ │ │ -public enum ValidationCondition permits ValidationCondition$2, ValidationCondition$1 │ │ +public enum ValidationCondition permits ValidationCondition$1, ValidationCondition$2 │ │ { │ │ CLUSTER_NEEDS_FINALIZATION("CLUSTER_NEEDS_FINALIZATION", 0), │ │ OLDER_CLIENT_REQUESTS("OLDER_CLIENT_REQUESTS", 1); │ │ │ │ private ValidationCondition(final String name, final int ordinal) { │ │ } ``` It affects `enum` types with constant-specific implementation (e.g. `abstract` method implemented in each constant). Since this is generated by the compiler, we would need a fix in OpenJDK. As a workaround, this PR converts such enums to switch-based implementation. https://issues.apache.org/jira/browse/HDDS-16557 ## How was this patch tested? https://github.com/adoroszlai/ozone/actions/runs/35832033343 -- 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]
