You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Péter Gergő Barna (JIRA)" <ji...@apache.org> on 2017/09/18 14:56:00 UTC
[jira] [Updated] (ATLAS-2132) Error code during invalid file
path/unreadable file provided during import
[ https://issues.apache.org/jira/browse/ATLAS-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Péter Gergő Barna updated ATLAS-2132:
-------------------------------------
Attachment: ATLAS-2132.patch
> Error code during invalid file path/unreadable file provided during import
> --------------------------------------------------------------------------
>
> Key: ATLAS-2132
> URL: https://issues.apache.org/jira/browse/ATLAS-2132
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.9-incubating
> Reporter: Sharmadha Sainath
> Assignee: Ashutosh Mestry
> Priority: Minor
> Attachments: ATLAS-2132.patch
>
>
> When firing import command using
> {code}
> /api/atlas/admin/importfile
> {code}
> when file provided in the import_options.json doesn't have read permission or file is not present , Atlas throws 500 Internal server error but with proper error message.
> Example :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException: invalid parameters: /exportimport/db5.zip: file not found"}
> {code}
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException: java.io.IOException: File '/exportimport/db6.zip' cannot be read"}
> {code}
> Expected that Atlas would throw 400 Bad Request instead of 500 Internal Server error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)