[
https://issues.apache.org/jira/browse/HIVE-26786?focusedWorklogId=829455&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-829455
]
ASF GitHub Bot logged work on HIVE-26786:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Nov/22 20:21
Start Date: 28/Nov/22 20:21
Worklog Time Spent: 10m
Work Description: ayushtkn opened a new pull request, #3810:
URL: https://github.com/apache/hive/pull/3810
### Why are the changes needed?
Read queries shouldn't fail for tables with copy-on-write mode
### Does this PR introduce _any_ user-facing change?
Yes, Read queries with copy-on-write will be successful.
### How was this patch tested?
Added UT.
Issue Time Tracking
-------------------
Worklog Id: (was: 829455)
Remaining Estimate: 0h
Time Spent: 10m
> Iceberg: Read queries with copy-on-write failing
> ------------------------------------------------
>
> Key: HIVE-26786
> URL: https://issues.apache.org/jira/browse/HIVE-26786
> Project: Hive
> Issue Type: Bug
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hive by default only supports merge-on-read, But the read queries have
> nothing to do with this config. The Read queries shouldn't fail due to this.
> The default mode set by Spark is copy-on-write, we should allow read
> operations on tables created via spark with copy-on-write
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
