[
https://issues.apache.org/jira/browse/ATLAS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151801#comment-15151801
]
Prasad S Madugundu commented on ATLAS-487:
-------------------------------------------
Hi Hemanth,
Yes, you got it right. Please refer to ATLAS-485
(https://issues.apache.org/jira/browse/ATLAS-485) for another example.
Please note that object level authorization capability does not work for our
case, where we would like to give authorization to a business classification or
a business domain (that maps to a number metadata objects in the repository),
instead of directly assigning the user/group to a specific metadata object. We
are planning to use tags for partitioning the metadata (based on business
classification or domain) and search the metadata by tags.
Thanks
> Externalize tag in search method
> --------------------------------
>
> Key: ATLAS-487
> URL: https://issues.apache.org/jira/browse/ATLAS-487
> Project: Atlas
> Issue Type: Improvement
> Reporter: Prasad S Madugundu
> Priority: Critical
>
> Tagging metadata (or adding traits to metadata) can be used for
> classification of metadata and metadata partitioning for multi-tenancy
> purpose or partition based on the organization hierarchy. In these use cases,
> it would be ideal if I can pass the trait as a separate parameter to the
> search method, instead of including the tag as a predicate in the query
> string.
> If I have a complex query that retrieves metadata from multiple types, then
> the query becomes more complex if I need to add predicates for the tags for
> all the types that are used in the query.
> Externalizing the tag from the search query would also lead to better
> structure for the client code, because I can add the classification or
> partition to the query without modifying the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
