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

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

                Author: ASF GitHub Bot
            Created on: 03/Jul/19 23:05
            Start Date: 03/Jul/19 23:05
    Worklog Time Spent: 10m 
      Work Description: miklosgergely commented on pull request #701: 
HIVE-21918 Handle each Alter Database types in a separate desc / operation
URL: https://github.com/apache/hive/pull/701
 
 
   Following the logic of the new DDL framework each operation type should have 
their own desc and operation. So far the 3 different Alter Database operations 
were handled in the same classes, now they are split.
 
----------------------------------------------------------------
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: 271917)
            Time Spent: 10m
    Remaining Estimate: 0h

> Handle each Alter Database types in a separate desc / operation
> ---------------------------------------------------------------
>
>                 Key: HIVE-21918
>                 URL: https://issues.apache.org/jira/browse/HIVE-21918
>             Project: Hive
>          Issue Type: Sub-task
>          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-21918.01.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> AlterDatabaseDesc / AlterDatabaseOperation handles all kind of alter database 
> commands. Following the logic of the DDL handling, they should be in separate 
> classes, with a mini framework handled by abstract ancestors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to