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

Chad Dombrova updated BEAM-7720:
--------------------------------
    Description: 
The contract in beam_job_api.proto for `CancelJobRequest`, 
`GetJobStateRequest`, and `GetJobPipelineRequest` states:

  
{noformat}
// Throws error NOT_FOUND if the jobId is not found{noformat}
  

However, `InMemoryJobService` is handling this exception incorrectly by 
rethrowing `NOT_FOUND` exceptions as `INTERNAL`.

neither `JobMessagesRequest` nor `GetJobMetricsRequest` state their contract 
wrt exceptions, but they should probably be updated to handle `NOT_FOUND` in 
the same way.

 

  was:
The contract in `beam_job_api.proto` for `CancelJobRequest`, 
`GetJobStateRequest`, and `GetJobPipelineRequest` states:

 

 
{noformat}
// Throws error NOT_FOUND if the jobId is not found{noformat}
 

 

However, `InMemoryJobService` is handling this exception incorrectly by 
rethrowing `NOT_FOUND` exceptions as `INTERNAL`.

neither `JobMessagesRequest` nor `GetJobMetricsRequest` state their contract 
wrt exceptions, but they should probably be updated to handle `NOT_FOUND` in 
the same way.

 


> Fix the exception type of InMemoryJobService when job id not found
> ------------------------------------------------------------------
>
>                 Key: BEAM-7720
>                 URL: https://issues.apache.org/jira/browse/BEAM-7720
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model
>            Reporter: Chad Dombrova
>            Priority: Major
>
> The contract in beam_job_api.proto for `CancelJobRequest`, 
> `GetJobStateRequest`, and `GetJobPipelineRequest` states:
>   
> {noformat}
> // Throws error NOT_FOUND if the jobId is not found{noformat}
>   
> However, `InMemoryJobService` is handling this exception incorrectly by 
> rethrowing `NOT_FOUND` exceptions as `INTERNAL`.
> neither `JobMessagesRequest` nor `GetJobMetricsRequest` state their contract 
> wrt exceptions, but they should probably be updated to handle `NOT_FOUND` in 
> the same way.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to