[ 
https://issues.apache.org/jira/browse/CAMEL-24207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-24207 started by Andrea Cosentino.
------------------------------------------------
> camel-aws2-transcribe: 21 declared operations are empty stubs that silently 
> do nothing
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24207
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24207
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-aws
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.22.0
>
>
> Transcribe2Operations declares 30 operations and Transcribe2Producer switches 
> on all of them, but 21 of the handler methods have empty bodies, e.g.:
> {code:java}
> private void createVocabularyFilter(TranscribeClient transcribeClient, 
> Exchange exchange) {
>     // Implementation for create vocabulary filter
> }
> {code}
> Selecting any of these operations is a *silent no-op*: no AWS call is made, 
> no error is raised, and the exchange passes through unchanged, so a route 
> appears to succeed while doing nothing.
> Affected operations: createVocabularyFilter, getVocabularyFilter, 
> listVocabularyFilters, updateVocabularyFilter, deleteVocabularyFilter, 
> createLanguageModel, describeLanguageModel, listLanguageModels, 
> deleteLanguageModel, createMedicalVocabulary, getMedicalVocabulary, 
> listMedicalVocabularies, updateMedicalVocabulary, deleteMedicalVocabulary, 
> startMedicalTranscriptionJob, getMedicalTranscriptionJob, 
> listMedicalTranscriptionJobs, deleteMedicalTranscriptionJob, tagResource, 
> untagResource, listTagsForResource.
> The header constants for these operations (VOCABULARY_FILTER_NAME, 
> LANGUAGE_MODEL_NAME, MEDICAL_TRANSCRIPTION_JOB_NAME, RESOURCE_ARN, TAGS, 
> TAG_KEYS, ...) already exist in Transcribe2Constants, so the operations were 
> clearly intended to work.
> Fix: implement all 21 operations following the pattern used by the working 
> operations (pojoRequest branch plus a header-driven branch), so the component 
> delivers the API it advertises.
> Code reference (main): Transcribe2Producer.java - the stub methods.
> Targeting 4.22.0 only: this adds a substantial amount of new behaviour and is 
> not appropriate for the maintenance branches.
> Found during an agent-assisted audit of the AWS components.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to