You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/01/10 07:28:00 UTC
[jira] [Updated] (ATLAS-2326) V1 API
/api/atlas/entities/ throws 500 Internal exception
[ https://issues.apache.org/jira/browse/ATLAS-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apoorv Naik updated ATLAS-2326:
-------------------------------
Attachment: 0002-ATLAS-2326-Error-code-fixes.patch
> V1 API /api/atlas/entities/<invalid_GUID> throws 500 Internal exception
> -----------------------------------------------------------------------
>
> Key: ATLAS-2326
> URL: https://issues.apache.org/jira/browse/ATLAS-2326
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Sharmadha Sainath
> Assignee: Apoorv Naik
> Attachments: 0002-ATLAS-2326-Error-code-fixes.patch, invalid_guid_exception.txt
>
>
> V1 API /api/atlas/entities/<invalid_GUID> throws 500 Internal server exception but with expected error message :
> {code}
> {
> error: "Given instance guid invalidGUIDkqDFDFNyb2zs5 is invalid\/not found"
> }
> {code}
> From application logs, we could see that it throws the Atlas Base Exception first , but later WebApplicationException is thrown.
> V2 API /api/atlas/v2/entity/<invalid_GUID> throws 404.
> Attached the complete stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)