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 2017/08/08 16:34:00 UTC

[jira] [Commented] (ATLAS-2026) Basic/DSL Query with invalid typeName/classification name throws 500 Internal server error

    [ https://issues.apache.org/jira/browse/ATLAS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118585#comment-16118585 ] 

Apoorv Naik commented on ATLAS-2026:
------------------------------------

I think it's better to do the validation in the search context itself, I've added a patch under ATLAS-2025

> Basic/DSL Query with invalid typeName/classification name throws 500 Internal server error
> ------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-2026
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2026
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>            Reporter: Sharmadha Sainath
>         Attachments: ATLAS-2026.2.patch, ATLAS-2026.patch
>
>
> Following DSL/Basic queries with invalid classification name and type name throw 500 Internal server error
> {code}
> http://localhost:21000/api/atlas/v2/search/basic?typeName=unknown_type&classification=unknown_tag
> http://localhost:21000/api/atlas/v2/search/dsl?typeName=unknown_type&classification=unknown_tag
> {code}
> It would be appropriate to throw 40X Error code instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)