atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Péter Gergő Barna (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names
Date Thu, 14 Sep 2017 07:58:00 GMT

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

Péter Gergő Barna resolved ATLAS-2121.
--------------------------------------
    Resolution: Duplicate

Resolving this as a duplicate of ATLAS-2117

> Inconsistency in basic search results due to case sensitivity of type names
> ---------------------------------------------------------------------------
>
>                 Key: ATLAS-2121
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2121
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.8-incubating, 0.9-incubating
>            Reporter: Sharmadha Sainath
>            Assignee: Péter Gergő Barna
>            Priority: Critical
>
> Type names are case sensitive hence 2 types can be created with different cases. 
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and 
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created, 
> and when a BASIC search is fired with
>  typeName= type1 , e1 is returned and
>  typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search , 
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and returns entity
tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct behavior.



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

Mime
View raw message