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

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

                Author: ASF GitHub Bot
            Created on: 31/May/22 00:20
            Start Date: 31/May/22 00:20
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #3007:
URL: https://github.com/apache/hive/pull/3007#issuecomment-1141553796

   This pull request has been automatically marked as stale because it has not 
had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the [email protected] list if the patch is in 
need of reviews.




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

    Worklog Id:     (was: 776064)
    Time Spent: 20m  (was: 10m)

> ValidWriteIdList & table id are sometimes missing when requesting partitions 
> by name via HS2
> --------------------------------------------------------------------------------------------
>
>                 Key: HIVE-25936
>                 URL: https://issues.apache.org/jira/browse/HIVE-25936
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> According to HIVE-24743 the table id and {{ValidWriteIdList}} are important 
> for keeping HMS remote metadata cache consistent. Although HIVE-24743 
> attempted to pass the write id list and table id in every call to HMS it 
> failed to do so completely. For those partitions not handled in the batch 
> logic, the [metastore 
> call|https://github.com/apache/hive/blob/4b7a948e45fd88372fef573be321cda40d189cc7/ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java#L4161]
>  in {{Hive#getPartitionsByName}} method does not pass the table id and write 
> id list.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to