[
https://issues.apache.org/jira/browse/HIVE-26670?focusedWorklogId=821684&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-821684
]
ASF GitHub Bot logged work on HIVE-26670:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/22 07:46
Start Date: 29/Oct/22 07:46
Worklog Time Spent: 10m
Work Description: abstractdog commented on PR #3710:
URL: https://github.com/apache/hive/pull/3710#issuecomment-1295762043
> +1 (non-binding)
>
> @abstractdog , thanks for your patience responding to the code review
feedback!
thanks a lot, @cnauroth for the quality code review!
Issue Time Tracking
-------------------
Worklog Id: (was: 821684)
Time Spent: 3h 20m (was: 3h 10m)
> Track every single HTTP request between beeline and hs2
> -------------------------------------------------------
>
> Key: HIVE-26670
> URL: https://issues.apache.org/jira/browse/HIVE-26670
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> In my use-case there is a couple of layers between beeline and hs2 (load
> balancer, proxies), and I'm about to add something to the requests
> (optionally), that can be simply written to access logs in as many layers as
> possible.
> So instead of:
> {code}
> 2022-10-18T04:34:25+00:00 - [10.80.143.240, 10.80.143.240] - [hs2 host] - [-]
> "POST /cliservice HTTP/1.1" 200 1069 "-" "Java/THttpClient/HC" 703 0.008...
> {code}
> I want to see something specific to the request, which is generated on client
> side, so client can also log it.
> As the title suggests, I'm targeting http transport.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
