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 2020/07/09 21:14:00 UTC

[jira] [Updated] (MADLIB-1442) Do not try to drop output tables

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

Frank McQuillan updated MADLIB-1442:
------------------------------------
    Priority: Minor  (was: Major)

> Do not try to drop output tables
> --------------------------------
>
>                 Key: MADLIB-1442
>                 URL: https://issues.apache.org/jira/browse/MADLIB-1442
>             Project: Apache MADlib
>          Issue Type: Improvement
>          Components: All Modules
>            Reporter: Orhan Kislal
>            Priority: Minor
>             Fix For: v1.18.0
>
>
> It seems MADlib drops the output table before creating a new one in some modules. We should not do this, instead, the user should be warned of the issue.
> In some cases, we first check if the output table exists and then try to drop the non-existent table anyway. We should remove these queries as well.
> The list of modules that might have this issue:
> Summary, assoc_rules, glm, pca_project, logistic regression



--
This message was sent by Atlassian Jira
(v8.3.4#803005)