hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-23516) Store hive replication policy execution metrics in the relational DB
Date Tue, 02 Jun 2020 18:00:00 GMT


ASF GitHub Bot logged work on HIVE-23516:

                Author: ASF GitHub Bot
            Created on: 02/Jun/20 17:59
            Start Date: 02/Jun/20 17:59
    Worklog Time Spent: 10m 
      Work Description: pkumarsinha commented on a change in pull request #1044:

File path: ql/src/java/org/apache/hadoop/hive/ql/scheduled/
@@ -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:
       We are relying  on conf.set(Constants.SCHEDULED_QUERY_NAMESPACE, q.getScheduleKey().getClusterNamespace());
With that context I am asking when is unsetClusterNamespace() called.

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:

Issue Time Tracking

    Worklog Id:     (was: 440364)
    Time Spent: 2h 50m  (was: 2h 40m)

> Store hive replication policy execution metrics in the relational DB
> --------------------------------------------------------------------
>                 Key: HIVE-23516
>                 URL:
>             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, Replication Metrics.pdf
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
> Details documented in the attached doc

This message was sent by Atlassian Jira

View raw message