You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Naima Djouhri (JIRA)" <ji...@apache.org> on 2016/01/14 17:31:39 UTC

[jira] [Assigned] (ATLAS-356) deleteTrait throws same exception for different error conditions

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

Naima Djouhri reassigned ATLAS-356:
-----------------------------------

    Assignee: Naima Djouhri

> deleteTrait throws same exception for different error conditions
> ----------------------------------------------------------------
>
>                 Key: ATLAS-356
>                 URL: https://issues.apache.org/jira/browse/ATLAS-356
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: David Kantor
>            Assignee: Naima Djouhri
>            Priority: Minor
>
> deleteTrait is throwing EntityNotFoundException when either the trait being deleted is not found on the entity or when the entity itself is not found.  This makes it difficult for callers to determine the actual error, as it forces them to parse the stack trace looking for a specific error message.  This is a brittle solution as messages can change and in the future are likely to be translated.  A specific exception should be thrown if the trait is not found as that is a very different condition which callers could handle as a non-error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)