[
https://issues.apache.org/jira/browse/ATLAS-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282238#comment-17282238
]
ASF subversion and git services commented on ATLAS-4127:
--------------------------------------------------------
Commit 5b3b0da9e95830c8cf6330bb218993717de9e0ff in atlas's branch
refs/heads/branch-2.0 from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5b3b0da ]
ATLAS-4127: Optimize Hive table calls in Atlas Hook
Signed-off-by: Sarath Subramanian <[email protected]>
(cherry picked from commit f848c9761bd340c9cbb790254420506d97c8e6b4)
> Reduce number of Hive table calls in Atlas Hook
> -----------------------------------------------
>
> Key: ATLAS-4127
> URL: https://issues.apache.org/jira/browse/ATLAS-4127
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 2.1.0
> Reporter: Deep Singh
> Assignee: Deep Singh
> Priority: Major
> Labels: hive-hooks
>
> In Atlas Hive bridge, while calculating processQualifiedName, all partitions
> are processed.
> For each partition, a hive call is made to get table details. Since multiple
> partitions can belong to the same table, there is a scope for improvement by
> avoiding repeated hive calls for the same table information.
> This improvement becomes crucial particularly in the case where there are
> several partitions for a single table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
