[ 
https://issues.apache.org/jira/browse/SQOOP-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Veena Basavaraj updated SQOOP-1820:
-----------------------------------
    Fix Version/s:     (was: 1.99.5)

> Wiki : Post Release Derby Repository Version Upgrade Guidelines
> ---------------------------------------------------------------
>
>                 Key: SQOOP-1820
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1820
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Veena Basavaraj
>
> We need  doc that clearly highlights what should be the process post release 
> to upgrade the repository version.
> Example for Derby and in future for PostGres
> In 1.99.4 release ( certain code that was committed to sqoop2 assuming it 
> would be in the next release did not make it to the cherry-pick list of 
> 1.99.4). this code was 
> {code}
>   if (repositoryVersion <= 4) {
>       
> runQuery(QUERY_UPGRADE_TABLE_SQ_CONFIG_ADD_UNIQUE_CONSTRAINT_NAME_TYPE_AND_CONFIGURABLE_ID,
>           conn);
>       
> runQuery(QUERY_UPGRADE_TABLE_SQ_INPUT_ADD_UNIQUE_CONSTRAINT_NAME_TYPE_AND_CONFIG_ID,
>  conn);
>     }
> {code}
> The check of 4 was made since that was the latest version of Derby
> {code}
>    */
>   public static final int LATEST_DERBY_REPOSITORY_VERSION = 4;
> {code}
> With this code not making the 1.99.4 ( note, the 4 and 1.99.4 have no 
> relation to the other, the derby version number is a incrementing sequence 
> that has not relation to the build version numbers, unlike the in house 
> connectors that seem to use the build version number)
> Anyways, now that we are in the next version potentially, the code should be 
> modified to say the current version is 5 and then this code needs to be 
> updated.
> See issue : https://issues.apache.org/jira/browse/SQOOP-1812
> All of this tribal knowledge is not in any wiki.
> Another related ticket is to fix the derby version number to use the build 
> version, so there is some sanity and not having to rely on a independently 
> increasing sequence number for repository version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to