[
https://issues.apache.org/jira/browse/MADLIB-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529301#comment-16529301
]
Jingyi Mei edited comment on MADLIB-1248 at 7/2/18 1:09 AM:
------------------------------------------------------------
This issue was caused by not returning 1 right after madpack calling
_append_uninstall_madlib_sqlfile and get return_signal == 1 see code here
([https://github.com/apache/madlib/blob/master/src/madpack/madpack.py#L1075).]
Thus madpack will keep going and calls _append_install_madlib_sqlfile which is
not needed.
was (Author: jingyimei):
This issue was caused by not returning 1 right after madpack calling
_append_uninstall_madlib_sqlfile and get return_signal == 1 see code here
([https://github.com/apache/madlib/blob/master/src/madpack/madpack.py#L1075).]
Thus madpack will keep going and calls _append_install_madlib_sqlfile which is
not needed.
> Reinstalling on a db that does not have MADlib
> ----------------------------------------------
>
> Key: MADLIB-1248
> URL: https://issues.apache.org/jira/browse/MADLIB-1248
> Project: Apache MADlib
> Issue Type: Bug
> Components: Madpack
> Reporter: Orhan Kislal
> Assignee: Jingyi Mei
> Priority: Major
>
> Reinstalling on a database that does not have MADlib already installed fails
> as expected. However, the info messages do not mention this failure. It seems
> the proper error message was lost during the `making madpack operations
> atomic` Jira (MADLIB-1242).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
