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

Mujtaba Chohan commented on PHOENIX-99:
---------------------------------------

Running the same upsert statement which was used with 2.x client, after upgrade 
with 3.0 client:
ERROR 203 (22005): Type mismatch. DATE and UNSIGNED_DATE for expression: 
'2013-01-04 01:01:01.000' in column CREATED_DATE (state=22005,code=203)
 



> Automatic white list based upgrade from 2.2 to 3.0
> --------------------------------------------------
>
>                 Key: PHOENIX-99
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-99
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 3.0.0
>
>         Attachments: coproc-tweak.diff, patch-3.diff, patch.diff, patch.diff
>
>
> Auto upgrade tables from Phoenix 2.2.2/2.2.3 format to Phoenix 3.0 format. 
> Note that upgrade is only attempted to be performed once, upon first 
> connection to a cluster. A table is only upgraded if it is white listed based 
> on the following new config property: phoenix.client.autoUpgradeWhiteList
> If this property is not present, no tables will be upgraded. The config 
> property may have the following values:
> - * which means upgrade everything or
> - a comma separated list of fully qualified, case sensitive names (note that 
> by default, Phoenix stores table names in uppercase unless put them in double 
> quotes at DDL time)
> Examples:
> {code}
>   <property>
>     <name>phoenix.client.autoUpgradeWhiteList</name>
>     <value>*</value> <!- will upgrade all tables ->
>   </property>
> {code}
> {code}
>   <property>
>     <name>phoenix.client.autoUpgradeWhiteList</name>
>     <value>MY_SCHEMA.MY_TABLE, OTHER_TABLE</value>
>   </property>
> {code}
> The upgrade is only run once per connection to a cluster (when the 
> SYSTEM.CATALOG is created). If you need to force it to run again after that, 
> you can remove or set to "false" the UpgradeTo30 value that's stored in the 
> metadata of the SYSTEM.CATALOG table.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to