sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Shreedharan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-659) Design metadata upgrade procedure
Date Fri, 19 Apr 2013 02:49:15 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635975#comment-13635975
] 

Hari Shreedharan commented on SQOOP-659:
----------------------------------------

Now that we are done with this, we need to:

* Add validation to the upgrade method.
* Move the cloneForms method to MForm class
* Add unit and integration tests.

There are probably a bunch of other things I missed - but these seem to be minimally required.
                
> Design metadata upgrade procedure
> ---------------------------------
>
>                 Key: SQOOP-659
>                 URL: https://issues.apache.org/jira/browse/SQOOP-659
>             Project: Sqoop
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: SQOOP-659-5.patch, SqoopMetadataUpgrade.pdf, SqoopMetadataUpgrade.pdf
>
>
> We need to have procedure for metadata upgrade in place before first release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message