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

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

                Author: ASF GitHub Bot
            Created on: 21/Jun/21 12:50
            Start Date: 21/Jun/21 12:50
    Worklog Time Spent: 10m 
      Work Description: marton-bod commented on pull request #2407:
URL: https://github.com/apache/hive/pull/2407#issuecomment-865006033


   Thanks @kuczoram , looks great! Just a few questions


-- 
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: 612607)
    Time Spent: 2h 10m  (was: 2h)

> Add tests to verify Hive can read/write after schema change on Iceberg table
> ----------------------------------------------------------------------------
>
>                 Key: HIVE-25264
>                 URL: https://issues.apache.org/jira/browse/HIVE-25264
>             Project: Hive
>          Issue Type: Test
>            Reporter: Marta Kuczora
>            Assignee: Marta Kuczora
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> We should verify if Hive can properly read/write Iceberg tables after their 
> schema was modified through the Iceberg API (it's like when an other engine, 
> like Spark has done modification on the schema). 
> Unit tests should be added for the following operations offered by the 
> UpdateSchema interface in the Iceberg API:
> - adding new top level column
> - adding new nested column
> - adding required column
> - adding required nested column
> - renaming a column
> - updating a column
> - making a column required
> - delete a column
> - changing the order of the columns in the schema



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

Reply via email to