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

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

                Author: ASF GitHub Bot
            Created on: 25/Jan/21 16:50
            Start Date: 25/Jan/21 16:50
    Worklog Time Spent: 10m 
      Work Description: mustafaiman commented on a change in pull request #1902:
URL: https://github.com/apache/hive/pull/1902#discussion_r563876100



##########
File path: ql/src/test/queries/clientnegative/bucket_mapjoin_mismatch1.q
##########
@@ -1,46 +0,0 @@
-set hive.strict.checks.bucketing=false;

Review comment:
       Removed tests are to test invalid hints which are not supported on Tez. 
It's been a long time since Tez is default engine. Nobody seems to miss them.




----------------------------------------------------------------
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: 541168)
    Time Spent: 50m  (was: 40m)

> Migrate NegativeCliDriver and NegativeMinimrCliDriver to llap
> -------------------------------------------------------------
>
>                 Key: HIVE-24673
>                 URL: https://issues.apache.org/jira/browse/HIVE-24673
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Mustafa İman
>            Assignee: Mustafa İman
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> These test drivers should run on llap. Otherwise we can run into situations 
> where certain queries correctly fail on MapReduce but not on Tez.
> Also, it is better if negative cli drivers does not mask "Caused by" lines in 
> test output. Otherwise, a query may start to fail for other reasons than the 
> expected one and we do not realize it.



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

Reply via email to