Claus Ibsen created CAMEL-25935:
-----------------------------------
Summary: camel-minio - the operation getObjectRange, as the
catalog and the documentation name it, fails at startup: the component calls it
getPartialObject
Key: CAMEL-25935
URL: https://issues.apache.org/jira/browse/CAMEL-25935
Project: Camel
Issue Type: Bug
Components: camel-minio
Affects Versions: 4.18.0, 4.22.0, 4.23.0
Reporter: Claus Ibsen
Fix For: 4.24.0
The {{operation}} option of minio lists {{getObjectRange}} among its values
({{MinioConfiguration}}, main 4065a7464c45, line 126), and so do the catalog
and the documentation ({{minio-component.adoc}}: the list of operations and the
example of the range). The enum the option binds to has {{getPartialObject}}
instead ({{MinioOperations}} line 28). So
{{minio:mybucket?operation=getObjectRange}} fails when the route starts:
{noformat}
java.lang.IllegalArgumentException: Enum class class
org.apache.camel.component.minio.MinioOperations does not have any constant
with value: getObjectRange
{noformat}
{{operation=getPartialObject}} works at runtime, but it is not a value of the
option in the catalog, so a validation of the endpoint reports it. Checked on
4.24.0-SNAPSHOT, the minio component against an S3 API. It is so since the
component was added (3.5.0); the component is deprecated since 4.23
(CAMEL-24750).
*Proposed change*: name the operation {{getObjectRange}} in the enum, as the
catalog, the documentation and the aws2-s3 and ibm-cos components do, and keep
{{getPartialObject}} working for the routes that use it.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
