Sharmadha Sainath created ATLAS-2124:
----------------------------------------
Summary: Difference is results of Basic search and DSL search when
an entity is associated to the child tag containing a super tag
Key: ATLAS-2124
URL: https://issues.apache.org/jira/browse/ATLAS-2124
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical
1.Created a tag super_tag .
2.Created a tag child_tag with superType as super_tag.
3.Associated an entity to child_tag.
4.Basic query :
{code}
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path&classification=child_tag
http://localhost:21000/api/atlas/v2/search/basic?typeName=hdfs_path&classification=super_tag
{code}
Both returned the entity.
DSL search :
{code}
http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path&classification=child_tag
{code}
returned the correct entity.
whereas
{code}
http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path&classification=super_tag
{code}
returned 0 results.
Following log is found in application.log for the DSL Search of tags.
{code}
WARN - [pool-1-thread-10 - 51ba13c9-493c-4c62-b11c-a8513ba771e9:] ~ Found
non-extractable argument '_().out('super_tag')' in the 'and' expression
'g.V().or(has('__typeName','hdfs_path'),has('__superTypeNames','hdfs_path')).as('a0').and(_().out('super_tag'))'
(ExpandAndsOptimization:111)
{code}
The above log is not specific to search with parent tag. Such log is printed
for search with child tags also.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
