[
https://issues.apache.org/jira/browse/HIVE-22873?focusedWorklogId=388278&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388278
]
ASF GitHub Bot logged work on HIVE-22873:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Feb/20 09:28
Start Date: 17/Feb/20 09:28
Worklog Time Spent: 10m
Work Description: miklosgergely commented on pull request #901:
HIVE-22873 schq ident
URL: https://github.com/apache/hive/pull/901#discussion_r380038310
##########
File path:
ql/src/java/org/apache/hadoop/hive/ql/scheduled/ScheduledQueryExecutionContext.java
##########
@@ -55,4 +66,8 @@ public long getProgressReporterSleepTime() {
return
conf.getTimeVar(ConfVars.HIVE_SCHEDULED_QUERIES_EXECUTOR_PROGRESS_REPORT_INTERVAL,
TimeUnit.MILLISECONDS);
}
+ public String getExecutorHostName() {
Review comment:
I'd suggest to declare all the global fields private, and have getters for
them, but if they should remain public, then no getter is necessary.
----------------------------------------------------------------
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: 388278)
Time Spent: 20m (was: 10m)
> Make it possible to identify which hs2 instance executed a scheduled query
> --------------------------------------------------------------------------
>
> Key: HIVE-22873
> URL: https://issues.apache.org/jira/browse/HIVE-22873
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-22873.01.patch, HIVE-22873.02.patch,
> HIVE-22873.03.patch, HIVE-22873.04.patch, HIVE-22873.05.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> right now only the query_id is shown; in case of multiple hs2 instances the
> question...users have to resort to grepping the logs for the given query
> id....
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
