Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-2124

Difference is results of Basic search and DSL search when an entity is associated to the child tag containing a super tag

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Not A Bug
    • 1.0.0
    • None
    • atlas-core
    • None

    Description

      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 :

      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
      

      Both returned the entity.

      DSL search :

      http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path&classification=child_tag
      

      returned the correct entity.

      whereas

      http://localhost:21000/api/atlas/v2/search/dsl?typeName=hdfs_path&classification=super_tag
      

      returned 0 results.

      Following log is found in application.log for the DSL Search of tags.

       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)
      

      The above log is not specific to search with parent tag. Such log is printed for search with child tags also.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sharmadhas Sharmadha S
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: