hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-23551) Acid: Update queries should treat dirCache as read-only in AcidUtils
Date Tue, 01 Sep 2020 00:47:01 GMT


ASF GitHub Bot logged work on HIVE-23551:

                Author: ASF GitHub Bot
            Created on: 01/Sep/20 00:46
            Start Date: 01/Sep/20 00:46
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #1047:

   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 list if the patch is in need of reviews.

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:

Issue Time Tracking

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

> Acid: Update queries should treat dirCache as read-only in AcidUtils
> --------------------------------------------------------------------
>                 Key: HIVE-23551
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>         Attachments: HIVE-23551.1.patch, HIVE-23551.2.patch, HIVE-23551.3.patch, HIVE-23551.4.patch,
HIVE-23551.5.patch, HIVE-23551.6.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Update statements create delta folders at the end of the execution. When {{insert overwrite}}
followed by {{update}} is executed, it does not get any open txns and ends up caching the {{base}}
folder. However, the delta folder which gets created at the end of the statement never makes
it to the cache. This creates wrong results.

This message was sent by Atlassian Jira

View raw message