You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@madlib.apache.org by "Frank McQuillan (JIRA)" <ji...@apache.org> on 2016/11/22 23:19:58 UTC

[jira] [Updated] (MADLIB-1041) Upgrade from 1.7.1->1.9 fails

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

Frank McQuillan updated MADLIB-1041:
------------------------------------
    Summary: Upgrade from 1.7.1->1.9 fails  (was: Upgrade from 1.7.1->1.9 and 1.7.1->1.9.1 fails)

> Upgrade from 1.7.1->1.9 fails
> -----------------------------
>
>                 Key: MADLIB-1041
>                 URL: https://issues.apache.org/jira/browse/MADLIB-1041
>             Project: Apache MADlib
>          Issue Type: Bug
>          Components: Madpack
>            Reporter: Frank McQuillan
>             Fix For: v1.10
>
>
> madpack upgrade from 1.7.1->1.9 failed with the following message:
> {code}
> madpack.py : INFO : Testing PL/Python environment...
> madpack.py : INFO : > PL/Python environment OK (version: 2.6.2)
> madpack.py : INFO : Upgrading MADlib into MADLIB schema...
> madpack.py : INFO :     Detecting dependencies...
> madpack.py : INFO :     Loading change list...
> madpack.py : INFO :     Detecting table dependencies...
> madpack.py : INFO :     Detecting view dependencies...
> madpack.py : INFO : No dependency problem found, continuing to upgrade ...
> madpack.py : ERROR : SQL command failed:
> SQL: DROP TYPE IF EXISTS madlib.svm_model_rec
> ERROR:  cannot drop type madlib.svm_model_rec because other objects depend on it
> HINT:  Use DROP ... CASCADE to drop the dependent objects too.
>  
> Exception:
> (<type 'exceptions.Exception'>, Exception(), <traceback object at 0xe4c2d8>)
> madpack.py : ERROR : MADlib upgrade failed.
> {code}
> I believe this error would happen on 1.7.1->1.9.1 and perhaps other cases as well.
> Please investigate and fix this bug, and also determine what madpack changes are required in the future to avoid this problem.



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