[CELEBORN-1607] Enable useEnumCaseInsensitive
for openapi-generator
#2754
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Enable
useEnumCaseInsensitive
for openapi-generator.And then in celeborn server end, the enum will be mapped to celeborn internal WorkerEventType.
Why are the changes needed?
I met exception when sending worker event with openapi sdk.
The testing code to re-produce:
Seems because for the EventTypeEnum, the name and value not the same and then cause this issue.
Not sure why the UT passed, but the integration testing failed.
For EventTypeEnum, because its value is case sensitive, so we meet this issue.
celeborn/openapi/openapi-client/src/main/java/org/apache/celeborn/rest/v1/model/SendWorkerEventRequest.java
Lines 47 to 83 in 8734d16
Related issue in jersey end I think, eclipse-ee4j/jersey#5288
In this PR,
useEnumCaseInsensitive
is enabled for openapi-generator.Does this PR introduce any user-facing change?
No, there is not user facing change and this SDK has not been released yet.
How was this patch tested?
Existing UT and Integration testing.