[
https://issues.apache.org/jira/browse/HIVE-25509?focusedWorklogId=681921&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-681921
]
ASF GitHub Bot logged work on HIVE-25509:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/21 10:44
Start Date: 16/Nov/21 10:44
Worklog Time Spent: 10m
Work Description: maheshk114 commented on pull request #2627:
URL: https://github.com/apache/hive/pull/2627#issuecomment-970145061
Code changes looks fine to me. +1
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 681921)
Time Spent: 20m (was: 10m)
> CLIService.closeOperation should not fail if operation handle is not present
> ----------------------------------------------------------------------------
>
> Key: HIVE-25509
> URL: https://issues.apache.org/jira/browse/HIVE-25509
> Project: Hive
> Issue Type: Bug
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I think, if we want the close operation to be safe and idempotent, we should
> not fail on client side if 2 different close requests come in (due to socket
> timeout + retry) for the same operation handle (and second fails because
> operation handle was already removed for the first request which then socket
> timed out)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
