[
https://issues.apache.org/jira/browse/ATLAS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194226#comment-15194226
]
CASSIO DOS SANTOS commented on ATLAS-487:
-----------------------------------------
[~yhemanth] I think that
[Atlas-491|https://issues.apache.org/jira/browse/ATLAS-491] is related but more
generic and at a higher level of abstraction than multi-tenancy considered in
this thread, where hierarchies are not involved. I wonder if that could be
implemented more efficiently (and securely) via some "lower-level" partitioning
of the data, possibly at the graph database layer? Ideally the storage layer
under Atlas should provide that type of capability so we were not required to
do any query rewriting.
> 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)
