[ 
https://issues.apache.org/jira/browse/HIVE-23516?focusedWorklogId=440388&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-440388
 ]

ASF GitHub Bot logged work on HIVE-23516:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Jun/20 18:43
            Start Date: 02/Jun/20 18:43
    Worklog Time Spent: 10m 
      Work Description: pkumarsinha commented on a change in pull request #1044:
URL: https://github.com/apache/hive/pull/1044#discussion_r434100727



##########
File path: 
ql/src/java/org/apache/hadoop/hive/ql/scheduled/ScheduledQueryExecutionService.java
##########
@@ -223,6 +223,10 @@ private void processQuery(ScheduledQueryPollResponse q) {
         HiveConf conf = new HiveConf(context.conf);
         conf.set(Constants.HIVE_QUERY_EXCLUSIVE_LOCK, 
lockNameFor(q.getScheduleKey()));
         conf.setVar(HiveConf.ConfVars.HIVE_AUTHENTICATOR_MANAGER, 
SessionStateUserAuthenticator.class.getName());
+        conf.set(Constants.SCHEDULED_QUERY_NAMESPACE, 
q.getScheduleKey().getClusterNamespace());

Review comment:
       Not the unset for conf conf.set(Constants.SCHEDULED_QUERY_NAMESPACE). 
What I am trying to find out is what happens if 'unsetClusterNamespace()' has 
been called from different flow and then this code 
   conf.set(Constants.SCHEDULED_QUERY_NAMESPACE, 
q.getScheduleKey().getClusterNamespace()); is called. Is that a possibility?




----------------------------------------------------------------
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: 440388)
    Time Spent: 3h 50m  (was: 3h 40m)

> Store hive replication policy execution metrics in the relational DB
> --------------------------------------------------------------------
>
>                 Key: HIVE-23516
>                 URL: https://issues.apache.org/jira/browse/HIVE-23516
>             Project: Hive
>          Issue Type: Task
>            Reporter: Aasha Medhi
>            Assignee: Aasha Medhi
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-23516.01.patch, HIVE-23516.02.patch, 
> HIVE-23516.03.patch, Replication Metrics.pdf
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> Details documented in the attached doc



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to