[ 
https://issues.apache.org/jira/browse/HIVE-25189?focusedWorklogId=608272&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-608272
 ]

ASF GitHub Bot logged work on HIVE-25189:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Jun/21 05:37
            Start Date: 08/Jun/21 05:37
    Worklog Time Spent: 10m 
      Work Description: pvary commented on pull request #2342:
URL: https://github.com/apache/hive/pull/2342#issuecomment-856458040


   @deniskuzZ: if I understand correctly, then here we have collected every 
table used by the query in the first phase of the compilation. If my 
understanding is correct, then we have a good place to request the locks for 
the tables and prevent / reduce race conditions during the compilation.
   @scarlin-cloudera, @deniskuzZ what do you think?
   
   Thanks, Peter 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 608272)
    Time Spent: 1h  (was: 50m)

> Cache the validWriteIdList in query cache before fetching tables from HMS
> -------------------------------------------------------------------------
>
>                 Key: HIVE-25189
>                 URL: https://issues.apache.org/jira/browse/HIVE-25189
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Steve Carlin
>            Assignee: Steve Carlin
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> For a small performance boost at compile time, we should fetch the 
> validWriteIdList before fetching the tables.  HMS allows these to be batched 
> together in one call.  This will avoid the getTable API from being called 
> twice, because the first time we call it, we pass in a null for 
> validWriteIdList.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to