[
https://issues.apache.org/jira/browse/HIVE-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620108#comment-16620108
]
Hive QA commented on HIVE-20349:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12940253/HIVE-20349.5.patch
{color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 14979 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/13895/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/13895/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-13895/
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: 12940253 - PreCommit-HIVE-Build
> Implement Retry Logic in HiveDruidSplit for Scan Queries
> --------------------------------------------------------
>
> Key: HIVE-20349
> URL: https://issues.apache.org/jira/browse/HIVE-20349
> Project: Hive
> Issue Type: Bug
> Components: Druid integration
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Priority: Major
> Attachments: HIVE-20349.1.patch, HIVE-20349.2.patch,
> HIVE-20349.3.patch, HIVE-20349.4.patch, HIVE-20349.5.patch, HIVE-20349.patch
>
>
> while distributing druid scan query we check where the segments are loaded
> and then each HiveDruidSplit directly queries the historical node.
> There are few cases when we need to retry and refetch the segments.
> # The segment is loaded on multiple historical nodes and one of them went
> down. in this case when we do not get response from one segment, we query the
> next replica.
> # The segment was loaded onto a realtime task and was handed over, when we
> query the realtime task has already finished. In this case there is no
> replica. The Split needs to query the broker again for the location of the
> segment and then send the query to correct historical node.
> This is also the root cause of failure of druidkafkamini_basic.q test, where
> the segment handover happens before the scan query is executed.
> Note: This is not a problem when we are directly querying Druid brokers as
> the broker handles the retry logic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
