[ 
https://issues.apache.org/jira/browse/HIVE-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612090#comment-16612090
 ] 

Hive QA commented on HIVE-19552:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12939305/HIVE-19552.1.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14936 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/13734/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13734/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13734/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12939305 - PreCommit-HIVE-Build

> Enable TestMiniDruidKafkaCliDriver#druidkafkamini_basic.q
> ---------------------------------------------------------
>
>                 Key: HIVE-19552
>                 URL: https://issues.apache.org/jira/browse/HIVE-19552
>             Project: Hive
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 3.1.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Nishant Bangarwa
>            Priority: Critical
>         Attachments: HIVE-19552.1.patch, HIVE-19552.patch
>
>
> The failure was caused by the following sequence of steps - 
> # Test queries for available hosts where a segment is located and gets the 
> location of kafka task. 
> # Kafka task hands over the data and finishes
> # Now the scan query is sent to the kafka task, but the task has already 
> completed and will fail. 
> https://issues.apache.org/jira/browse/HIVE-20349 fixes this issue by retrying 
> the broker in this case. 
> One more cause of failure was the latestOffsets and minimumLag not reported 
> when there is no task. 
> This patch masks those two values also. Query results are verified to ensure 
> that there is no lag. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to