But I dont have Kerberos or LDAP. Regarding Ranger policies, that's exactly what I have, but still can perform actions on Hiveserver2 using the username and no password (or wrong password, doesnt matter). I think I am missing something in Ranger configuration. I mean: when I limit user permission for Hive (only Select permission in one DB). I can Select on that DB, but with no password. So, I dont know if this is Ranger or Hive issue. ... View more

Yes, it is. You can use the following Rest call: GET http://<atlas-server-host:port>/api/atlas/discovery/search/dsl?query=%60Catalog.Marketing.Customers%60 The JSON Response will be like this: { "requestId": string, "query": trait_name_within_backticks, "queryType": "dsl", "count": int, "results": [{ "$typeName$": "__tempQueryResultStruct...", "instanceInfo": { "$typeName$": "__IdType", "guid": guid of entity associated to trait or term, "typeName": type of entity associated to trait or term }, "traitDetails": null }, ....], "dataType": { "typeName": "__tempQueryResultStruct...", "typeDescription": null, "attributeDefinitions": [{ "name": "traitDetails", "dataTypeName": trait or term name, "multiplicity": { "lower": 0, "upper": 1, "isUnique": false }, "isComposite": false, "isUnique": false, "isIndexable": true, "reverseAttributeName": null }, { "name": "instanceInfo", "dataTypeName": "__IdType", "multiplicity": { "lower": 0, "upper": 1, "isUnique": false }, "isComposite": false, "isUnique": false, "isIndexable": true, "reverseAttributeName": null }] } } So, you're getting the GUID of the entities associated with your trait. Best Regards, Ivan Diaz. ... View more

Hi Subash, I've tried to perform a search just like yours and you're right: it's not showing $traits$ key. I tried something that worked for me: in your Rest End Point change the %22 to %27, just like this: atlas_hostname + '/api/atlas/discovery/search/dsl?query=hive_table+where+db.name%3D%27'+ database + '%27&limit=10000' I think it'll work. Best Regards, Ivan. ... View more