[
https://issues.apache.org/jira/browse/ATLAS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-487.
------------------------------------
Fix Version/s: 1.0.0
Resolution: Done
Basic-search APIs allow classification names (aka trait-names) to be specified
in a separate parameter. This Jira also talks about object-level authorization,
which is available in the authorization model introduced in ATLAS-2459.
> 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: Major
> Fix For: 1.0.0
>
>
> 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
(v8.3.4#803005)
