You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Chad Dombrova (JIRA)" <ji...@apache.org> on 2019/08/15 05:54:00 UTC
[jira] [Assigned] (BEAM-7720) Fix the exception type of
InMemoryJobService when job id not found
[ https://issues.apache.org/jira/browse/BEAM-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chad Dombrova reassigned BEAM-7720:
-----------------------------------
Assignee: Chad Dombrova
> 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
> Assignee: Chad Dombrova
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.14#76016)