@subash sharma , add limit parameter like : /api/atlas/discovery/search/dsl?query=hive_table+where+db.name%3D%22default%22&limit=500 ... View more

Welcome @subash sharma . Please accept the answer if it answered your question. ... View more

@Gnanasekaran G check NULL is NULL instead of NULL = NULL. This worked for me. ... View more

@Poorvi Sachar If it shows "Lineage not found" , it is not an exception or error . It means that actually there is no Lineage. ... View more

How long does it take for other APIs ? Atlas server might be residing in a remote location and you might be pinging from your local machine hence there can be network delay. Can you please login to the machine and do curl GET of the same APIs and add -w to curl to check the time taken ? Also, >> I guess the request is taking too long to process and hence empty vertices and edges are recieved in the JSON Response. This is not true. UI says "Lineage not found" when there is really no lineage data. Truthfulness of this API response doesn't depend on the time taken. We should debug why the API call takes long time. ... View more

Truncating the hbase tables atlas_titan , ATLAS_ENTITY_AUDIT_EVENTS would work. ... View more

Either Solr or Elastic Search should be installed and started for Atlas to start up. Indexing backend is a hard dependency for Atlas. ... View more

You might be interested in 1. http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_data-governance/content/ch_hdp_data_governance_overview.html#atlas_ranger_integration 2. http://hortonworks.com/hadoop-tutorial/tag-based-policies-atlas-ranger/ ... View more