[ https://issues.apache.org/jira/browse/ATLAS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apoorv Naik resolved ATLAS-2019. -------------------------------- Resolution: Fixed Fix Version/s: 0.8-incubating trunk > Search using entity and trait attributes - Equals comparison using filter key > when filter key is present between special characters > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: ATLAS-2019 > URL: https://issues.apache.org/jira/browse/ATLAS-2019 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Affects Versions: 0.9-incubating > Reporter: Sharmadha Sainath > Assignee: Apoorv Naik > Fix For: trunk, 0.8-incubating > > > 1. Created hdfs_path entity with name = "user" , path = "/user" > 2. Created another hdfs_path with name="dir1" , path = "/user/dir1" > 3. Searched for hdfs_path , filter Path = /user > 4. The search listed down both the hdfs_path entities - user and dir1. > Expected that only "user" entity would be returned. > Here, the filter key is "/user" and if the filter key is present between > special characters in the attribute values ( "/" in this case) , all those > entities are returned. > Please note that , filter applied is "=" and not "contains" > Created few random hdfs_path entities for testing : > For the query type ="hdfs_path" and path = "/user" , entities with following > path attribute values are returned : > * user > * /user > * user/ > * /user/dir1 > * @user@dir1 > * /user@dir1 > Entities with following path values are *NOT* returned > * /userdir1 > * rootuser/dir2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)