Umesh Padashetty created RANGER-5196:
----------------------------------------
Summary: Newly added tag attributes are not return by Ranger Tag
REST APIs
Key: RANGER-5196
URL: https://issues.apache.org/jira/browse/RANGER-5196
Project: Ranger
Issue Type: Bug
Components: tagsync
Reporter: Umesh Padashetty
For instance, take this tag test_tag_7bf80d08_1744215889 defined in atlas,
Ranger GET /tags/tagdefs returns
{code:java}
{
"id": 155,
"guid": "6b8e2431-31e3-44d7-aef6-4f97555d7e02",
"isEnabled": true,
"createdBy": "rangertagsync",
"updatedBy": "rangertagsync",
"createTime": 1744215891278,
"updateTime": 1744215891280,
"version": 1,
"name": "test_tag_7bf80d08_1744215889",
"source": "Atlas",
"attributeDefs": [
{
"name": "date_attr",
"type": "string"
},
{
"name": "int_attr",
"type": "string"
},
{
"name": "bool_attr",
"type": "string"
},
{
"name": "string_attr",
"type": "string"
},
{
"name": "float_attr",
"type": "string"
}
]
} {code}
I added another attribute testing_version_attribute with type "bool" in atlas.
I then went on to add this new value in the entity previously assigned to this
tag.
After invoking Ranger GET /tags/tagdefs returns, ideally the newly added tag
attribute testing_version_attribute should be returned by Ranger Tag REST APIs.
But they are not being returned.
It is also observed that the policy enforcement works fine based on updated tag
because the version change happens in policy-cache. It is just that the REST
APIs are still returning old/stale data. This should be addressed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
