[
https://issues.apache.org/jira/browse/HIVE-21292?focusedWorklogId=202543&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-202543
]
ASF GitHub Bot logged work on HIVE-21292:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/19 11:03
Start Date: 22/Feb/19 11:03
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on pull request #543: HIVE-21292:
Break up DDLTask 1 - extract Database related operations
URL: https://github.com/apache/hive/pull/543#discussion_r259296712
##########
File path:
ql/src/java/org/apache/hadoop/hive/ql/exec/ddl/database/SwitchDatabaseDesc.java
##########
@@ -16,37 +16,34 @@
* limitations under the License.
*/
-package org.apache.hadoop.hive.ql.plan;
+package org.apache.hadoop.hive.ql.exec.ddl.database;
import java.io.Serializable;
-import org.apache.hadoop.hive.ql.plan.Explain.Level;
+import org.apache.hadoop.hive.ql.exec.ddl.DDLDesc;
+import org.apache.hadoop.hive.ql.exec.ddl.DDLTask2;
+import org.apache.hadoop.hive.ql.plan.Explain;
+import org.apache.hadoop.hive.ql.plan.Explain.Level;
/**
- * SwitchDatabaseDesc.
- *
+ * DDL task description for SWITCH DATABASE commands.
Review comment:
`SWITCH DATABASE` :)
I'm not aware if that's a valid statment - is it? :)
I usually use `USE db1` ; can we rename things around here to something like
`UseDatabaseDesc` ?
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/Alter/UseDatabase
according to:
```
$ git grep -i switch|grep -i database|grep -v HOOK:|grep -v java:|grep -v
q.out|grep -v js:|less
ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g:TOK_SWITCHDATABASE;
ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g: |
switchDatabaseStatement
ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g:switchDatabaseStatement
ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g:@init {
pushMsg("switch database statement", state); }
ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g: ->
^(TOK_SWITCHDATABASE identifier)
ql/src/test/queries/clientnegative/database_switch_does_not_exist.q:-- Try
to switch to a database that does not exist
```
"switchdatabase" is also the keyword in the `HiveParser`
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 202543)
Time Spent: 2h 20m (was: 2h 10m)
> Break up DDLTask 1 - extract Database related operations
> --------------------------------------------------------
>
> Key: HIVE-21292
> URL: https://issues.apache.org/jira/browse/HIVE-21292
> 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, HIVE-21292.05.patch
>
> Time Spent: 2h 20m
> 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
(v7.6.3#76005)
