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-21292) Break up DDLTask 1 - extract Database related operations
Date Fri, 22 Feb 2019 12:34:00 GMT


ASF GitHub Bot logged work on HIVE-21292:

                Author: ASF GitHub Bot
            Created on: 22/Feb/19 12:33
            Start Date: 22/Feb/19 12:33
    Worklog Time Spent: 10m 
      Work Description: miklosgergely commented on pull request #543: HIVE-21292: Break up
DDLTask 1 - extract Database related operations

 File path: ql/src/java/org/apache/hadoop/hive/ql/exec/ddl/
 @@ -0,0 +1,75 @@
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.hadoop.hive.ql.exec.ddl;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.hadoop.hive.conf.HiveConf;
+import org.apache.hadoop.hive.ql.DriverContext;
+import org.apache.hadoop.hive.ql.metadata.Hive;
+import org.apache.hadoop.hive.ql.metadata.HiveException;
+import org.apache.hadoop.hive.ql.metadata.formatting.MetaDataFormatUtils;
+import org.apache.hadoop.hive.ql.metadata.formatting.MetaDataFormatter;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+ * Abstract ancestor class of all DDL Operation classes.
+ */
+public abstract class DDLOperation<T extends DDLDesc> {
+  protected static final Logger LOG = LoggerFactory.getLogger("hive.ql.exec.DDLTask");
+  protected Hive db;
 Review comment:
   Have considered it, but as they are populated via the init method they can not be final.
passing them via constructor would help, but then all the operation classes should have a
constructor with the same arguments just to pass these variables...
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 202600)
    Time Spent: 3h 50m  (was: 3h 40m)

> Break up DDLTask 1 - extract Database related operations
> --------------------------------------------------------
>                 Key: HIVE-21292
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive
>    Affects Versions: 3.1.1
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>         Attachments: HIVE-21292.01.patch, HIVE-21292.02.patch, HIVE-21292.03.patch, HIVE-21292.04.patch,
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
> DDLTask is a huge class, more than 5000 lines long. The related DDLWork is also a huge
class, which has a field for each DDL operation it supports. The goal is to refactor these
in order to have everything cut into more handleable classes under the package  org.apache.hadoop.hive.ql.exec.ddl:
>  * have a separate class for each operation
>  * have a package for each operation group (database ddl, table ddl, etc), so the amount
of classes under a package is more manageable
>  * make all the requests (DDLDesc subclasses) immutable
>  * DDLTask should be agnostic to the actual operations
>  * right now let's ignore the issue of having some operations handled by DDLTask which
are not actual DDL operations (lock, unlock, desc...)
> In the interim time when there are two DDLTask and DDLWork classes in the code base the
new ones in the new package are called DDLTask2 and DDLWork2 thus avoiding the usage of fully
qualified class names where both the old and the new classes are in use.
> Step #1: extract all the database related operations from the old DDLTask, and move them
under the new package. Also create the new internal framework.

This message was sent by Atlassian JIRA

View raw message