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

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

                Author: ASF GitHub Bot
            Created on: 21/Apr/21 07:51
            Start Date: 21/Apr/21 07:51
    Worklog Time Spent: 10m 
      Work Description: marton-bod commented on a change in pull request #2193:
URL: https://github.com/apache/hive/pull/2193#discussion_r617283836



##########
File path: 
iceberg/iceberg-handler/src/test/java/queries/negative/create_iceberg_table_failure.q
##########
@@ -0,0 +1,2 @@
+set hive.vectorized.execution.enabled=true;

Review comment:
       Can we add here other table creation failure scenarios too? One that 
comes to mind now is where you specify a PARTITIONED BY clause but also specify 
the json spec in the table properties. Another one could be related to type 
mismatches, i.e. using an unsupported Hive type, like interval in the columns




-- 
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: 586386)
    Time Spent: 2h  (was: 1h 50m)

> Create TestIcebergCliDriver and TestIcebergNegativeCliDriver
> ------------------------------------------------------------
>
>                 Key: HIVE-25010
>                 URL: https://issues.apache.org/jira/browse/HIVE-25010
>             Project: Hive
>          Issue Type: Test
>            Reporter: László Pintér
>            Assignee: László Pintér
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> We should create iceberg specific drivers to run iceberg qtests.



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

Reply via email to